MoodleDocs - Wkład użytkownika [pl]

Parent role

2010-12-14T18:31:15Z

Matthewm1970: /* Viewing activity reports */

The role of '''Parent''' may be used to provide parents/mentors/tutors with permission to view certain information, such as activity reports, grades, blog entries and forum posts, about their children/mentees/tutees.

==Role set-up==

#Access ''Administration > Users > Permissions > Define roles''
#Click the button "Add a new role"
#Give the role a name e.g. Parent, short name and description
#Change [[Capabilities/moodle/user:viewdetails|moodle/user:viewdetails]] to ''allow'' - this item is listed within the 'Course' section in 1.9
#Change any/all of the following capabilities to ''allow''
#*[[Capabilities/moodle/user:readuserblogs|moodle/user:readuserblogs]] - to read the child's blog entries
#*[[Capabilities/moodle/user:readuserposts|moodle/user:readuserposts]] - to read the child's forum posts
#*[[Capabilities/moodle/user:viewuseractivitiesreport|moodle/user:viewuseractivitiesreport]] - to view the child's activity reports and grades
#*[[Capabilities/moodle/user:editprofile|moodle/user:editprofile]] - to edit the child's profile
#Click the button "Add a new role"

==Role assignment==

#Access the child's profile page and click on the Roles tab i.e. assign the role in the user context
#Choose the role to assign i.e. Parent
#Select the parent in the potential users list, and use the left-facing arrow button to add it to the existing users list
The same parent may be assigned to several children.
===Adding multiple role assignments at once===
(if you are interested in assigning several parent roles ''en masse'' read the discussion at http://moodle.org/mod/forum/discuss.php?d=70539#p345127)

==Mentees block==
{{Moodle 1.8}}
The [[Mentees block]] provides a parent with quick access to their child's profile page via a link on the site front page.
#On the site front page click "Turn editing on"
#Choose Mentees from the Add a block drop-down menu
#If required, give the Mentees block a title by following the block configuration/edit link

==Viewing activity reports==

If the capability [[Capabilities/moodle/user:viewuseractivitiesreport|moodle/user:viewuseractivitiesreport]] is set to ''allow'' then a parent/mentee may view their student's activity reports and grades via the student's Profile.

On the main Profile page, there will be a list of courses. Clicking on a course title will select that course. Then, under the Activities tab, the various report and grades sub-tabs will display information relevant to the selected course. You can easily change which course you are reviewing by selecting another one on the main Profile tab.

One small hack that can make the course list a bit more readable, especially for long course lists, is to change the format to a vertical list:

* Edit the moodle/user/view.php file and look for these lines (around line 349 in my 1.9.9 installation):
<code php>. format_string($mycourse->fullname) . "</a>, ";
}
else {
$courselisting .= format_string($mycourse->fullname) . ", ";</code>
* and change that to :
<code php>. format_string($mycourse->fullname) . "</a> ";
}
else {
$courselisting .= format_string($mycourse->fullname) . " ";;</code>
* Then save

==See also==
*[[Manage roles]] - including testing a new role
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=57812 Create a Parent of a student role] forum discussion
*[http://www.youtube.com/watch?v=-49YrtjMTTo Setting up a Parent Role video]
*[http://www.youtube.com/watch?v=P23GT2peLZI Parent Signing in on Moodle video]

[[Category:Roles]]

[[eu:Guraso_rola]]
[[fr:Rôle Parent]]
[[ja:親ロール]]
[[de:Eltern-Rolle]]
[[nl:Ouder Rol]]

Parent role

2010-12-14T17:44:38Z

Matthewm1970:

The role of '''Parent''' may be used to provide parents/mentors/tutors with permission to view certain information, such as activity reports, grades, blog entries and forum posts, about their children/mentees/tutees.

==Role set-up==

#Access ''Administration > Users > Permissions > Define roles''
#Click the button "Add a new role"
#Give the role a name e.g. Parent, short name and description
#Change [[Capabilities/moodle/user:viewdetails|moodle/user:viewdetails]] to ''allow'' - this item is listed within the 'Course' section in 1.9
#Change any/all of the following capabilities to ''allow''
#*[[Capabilities/moodle/user:readuserblogs|moodle/user:readuserblogs]] - to read the child's blog entries
#*[[Capabilities/moodle/user:readuserposts|moodle/user:readuserposts]] - to read the child's forum posts
#*[[Capabilities/moodle/user:viewuseractivitiesreport|moodle/user:viewuseractivitiesreport]] - to view the child's activity reports and grades
#*[[Capabilities/moodle/user:editprofile|moodle/user:editprofile]] - to edit the child's profile
#Click the button "Add a new role"

==Role assignment==

#Access the child's profile page and click on the Roles tab i.e. assign the role in the user context
#Choose the role to assign i.e. Parent
#Select the parent in the potential users list, and use the left-facing arrow button to add it to the existing users list
The same parent may be assigned to several children.
===Adding multiple role assignments at once===
(if you are interested in assigning several parent roles ''en masse'' read the discussion at http://moodle.org/mod/forum/discuss.php?d=70539#p345127)

==Mentees block==
{{Moodle 1.8}}
The [[Mentees block]] provides a parent with quick access to their child's profile page via a link on the site front page.
#On the site front page click "Turn editing on"
#Choose Mentees from the Add a block drop-down menu
#If required, give the Mentees block a title by following the block configuration/edit link

==Viewing activity reports==

If the capability [[Capabilities/moodle/user:viewuseractivitiesreport|moodle/user:viewuseractivitiesreport]] is set to ''allow'' then a parent may view their child's activity reports and grades. To access the activity reports and grades for each of their child's courses, the parent should follow each of the course links on their child's profile page.

==See also==
*[[Manage roles]] - including testing a new role
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=57812 Create a Parent of a student role] forum discussion
*[http://www.youtube.com/watch?v=-49YrtjMTTo Setting up a Parent Role video]
*[http://www.youtube.com/watch?v=P23GT2peLZI Parent Signing in on Moodle video]

[[Category:Roles]]

[[eu:Guraso_rola]]
[[fr:Rôle Parent]]
[[ja:親ロール]]
[[de:Eltern-Rolle]]
[[nl:Ouder Rol]]

Cron

2010-11-02T20:34:52Z

Matthewm1970:

Cron is the name of a Unix program that runs predefined tasks on a computer at regular intervals. It assists some of Moodle's modules to perform tasks on a scheduled basis. For example, the cron process might tell Moodle to check all discussion forums so it can mail out copies of new posts to people who have subscribed to that forum.

The primary Moodle script that does all this is located in the admin directory, and is called cron.php. However, it can not tell itself to run, so you need to set up a mechanism where this script is run regularly (eg every five or ten minutes). This provides a "heartbeat" so that the script can perform functions at periods defined by each module. This kind of regular mechanism is known as a '''cron service'''. The service can be part of a webhost or can be something run from a different server or computer.

==Overview of cron==
===Script overview===

The cron.php script looks through the mdl_modules table (assuming the default table prefix is mdl_) in the Moodle database for modules scheduled to have their cron functions run; it then looks in each such module directory for a function called module-name_cron in the lib.php file and runs it. It also looks through the mdl_block table for blocks scheduled for their cron methods (object functions) to be run; it then, for each such block, runs the cron method for a new object associated with that block (I'm omitting details for the benefit of non-programmers; programmers can read admin/cron.php for themselves). These files (the lib.php files and the files where the block classes are defined) can contain cleanup functions, email functions or anything that needs to be run on a regular basis. For example, cron will trigger the system to create the backups of courses at the time specified in the administration settings. It also triggers any messaging module or forum email notifications, but not all functions are called each time the cron runs. Some functions, such as unenrolling students who have not logged in or deleting old copies of log files, are only run occasionally. The cron.php file has a section which will randomly call these core tasks approximately 1 in 5 times the cron runs.

===Starting cron===
In Moodle 1.9 there are a number of way to invoke cron.php. Cron can be started from the address bar in a browser (URL usually ending in admin/cron.php), via a [[Daemon]], or wq1et, curl or some other code.

The cron process can be protected by a password.

The cronclionly Security> Site Policies setting with stop the broswer URL trigger. This sets Moodle so that cron.php cannot be invoked by the Moodle URL. See the illustration below.

'''Menu: Security > Site policies'''

[[Image:Moodelcronadmin.png]]

:''TIP:'' While this is identified as CLI (command line interface) this is a bit misleading in that it does not mean that you have to be sitting at a shell account entering the command. If you enable this switch you can invoke cron.php through any set of batch or script files you wish, but it must be invoked via its correct location in the operating systems file structure. This can be especially frustrating for those not used to scripting in that environment is not typically provided.

===Cron service location and timing===
Note that the machine performing the cron '''does not need to be the same machine that is running Moodle'''. For example, if you have a limited web hosting service that does not have a cron service, then you 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.

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. Remember that mail-outs also wait for the editing time to expire before being queued for sending.

===Testing cron and manual trigger===

First, test that the script works by running it directly from your browser: ''<nowiki>http://example.com/moodle/admin/cron.php</nowiki>''

If cron is called from the command line by any user logged in to your Moodle it will create a temporary admin environment in order to run and then log the user out. You can disable command line running of cron by disabling the appropriate section in the cron.php file.

Now, you need to set up some of way of running the script automatically and regularly.

==Managing Cron on Windows systems==

There are two different ways for setting-up Moodle cron.php on Windows systems:

*Use the '''Moodle Cron package'''. The simplest way is to use this little package [http://download.moodle.org/download.php/windows/MoodleCron-Setup.exe MoodleCron-Setup.exe], which makes this whole thing very easy by installing a small Windows service. Run it and forget about it! :-)
*Use a '''Scheduled Task'''. If you prefer to use the built-in Windows Scheduler or are having trouble with moodle-cron-for-windows package, you can use wget for windows or php from the command line and setup a scheduled task. Just follow these steps:
** Choose either the '''php.exe/php-win.exe (command line binary)''' or '''wget'''
::The php.exe or php-win.exe binary (for PHP version 5 or later) is installed in your php folder (e.g. c:\php) will give you better performance when running the cron script.
::If you want to use wget, download a compiled version of wget for windows from the native GNU Win32 ports (http://unxutils.sourceforge.net/), from Heiko Herold's wget for windows page (http://xoomer.virgilio.it/hherold/) or Bart Puype's wget for windows page (http://users.ugent.be/~bpuype/wget/). If you use Heiko Herold's package, copy all of the .DLL files to your C:\Windows\system32 directory. Copy the wget.exe file to c:\windows (this makes sure wget is always in the search path).
:* Setup a '''Scheduled Task'''.
:: - Go to Start >> Control Panel >> Scheduled Tasks >> Add Scheduled Task.
:: - Click "Next" to start the wizard:
:: - Click in the "Browse..." button and browse to c:\php\php.exe or c:\windows\wget.exe and click "Open"
:: - Type "Moodle Cron" as the name of the task and select "Daily" as the schedule. Click "Next".
:: - Select "12:00 AM" as the start time, perform the task "Every Day" and choose today's date as the starting date. Click "Next".
:: - Enter the username and password of the user the task will run under (it doesn't have to be a priviledged account at all). Make sure you type the password correctly. Click "Next".
:: - Mark the checkbox titled "Open advanced properties for this task when I click Finish" and click "Finish".
:: - In the new dialog box, type the following in the "Run:" text box: <pre>c:\windows\wget.exe -q -O NUL http://my.moodle.site/moodle/admin/cron.php</pre> or <pre>c:\php\php-win.exe -f c:\moodle\admin\cron.php</pre> Replace "c:\moodle" with the path to your moodle directory or "my.moode.site" with the name of your site. 
:: - Click on the "Schedule" tab and there in the "Advanced..." button.
:: - Mark the "Repeat task" checkbox and set "Every:" to 5 minutes, and set "Until:" to "Duration" and type "23" hours and "59" minutes.
:: - Click "OK" and you are done.
* '''Test your scheduled task'''. You can test that your scheduled task can run successfully by clicking it with the right button and chosing "Run". If everything is correctly setup, you will briefly see a DOS command window while wget/php executes and fetches the cron page and then it disappears. If you refresh the scheduled tasks folder, you will see the ''Last Run Time column'' (in detailed folder view) reflects the current time, and that the Last Result column displays "0x0" (everything went OK). If either of these is different, then you should recheck your setup.
* '''Logging cron output'''. You may want to log the output of the cron script as it executes, in case you see the job is producing errors, backups are not being completed or users are experiencing delays in receiving forum emails. To do this, adjust the command so that it uses the php.exe and stores the output in a file called (for example c:\moodle\admin\cron.log). Here is an example of the php.exe command:
<pre>c:\php\php.exe -f c:\moodle\admin\cron.php > c:\moodle\admin\cron.log</pre>
If you experience problems logging the output of cron.php to a text file using the above command then read [http://moodle.org/mod/forum/discuss.php?d=139263#p609060 this] message by Iñaki Arenaza for an alternative way to log the output of Cron.

==Managing the cron job on Mac OS X with launchd==

It's really important to start the cron job every 5 minutes. The cron job assists most of Moodle's modules to perform tasks on a scheduled basis. For example, the discussion forums can only mail out copies of new posts to all subscribers if the cron job tells Moodle to do this.

In Mac OS X 10.5 you will find the system daemon ''launchd'' for this service. This daemon offers a standardized interface to any user and all programs started automatically by the system. Please look at http://developer.apple.com/macosx/launchd.html for more informations about the configurations and all parameters.

In our case the service should get the web page http://your-server-address/moodle19/admin/cron.php every 5 minutes. The configuration will be done by the file named ''moodle4mac.cron.plist'' which must be placed in the system folder ''/Library/LaunchDaemons/'' ... surely you can use any other file name but it should say something about the function of the service. The extension must be ''.plist''. After any reboot of your Mac server the cron service will start automaticly because the file is placed in the correct system folder.

===Use the graphical way===
You can use Lingon to add a new daemon plist or to edit one. It produces the same text as you can write in your text editor. http://sourceforge.net/projects/lingon/files/

[[Image:macosx-lingon.png]]

===Use a text editor===
Please use a text editor to write the needed file. You can open the Terminal and use the system editors vi or pico. But you can also write the text file with any GUI text editor ... I mostly use TextWrangler ... but do NOT take an editor for formatted texts like Microsoft Word or OpenOffice Writer. You must get pure text!

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>KeepAlive</key><false/>
<key>Label</key><string>moodle4mac.cron</string>
<key>ProgramArguments</key>
<array>
<string>curl</string>
<string>-s</string>
<string>http://your-server-address/moodle19/admin/cron.php</string>
</array>
<key>RunAtLoad</key><true />
<key>StartInterval</key><integer>300</integer>
<key>StandardErrorPath</key><string>/dev/null</string>
<key>StandardOutPath</key><string>/dev/null</string>
</dict>
</plist>

The label string must be the same as the file name is but without the extension ''.plist''. Save the text file ''/Library/LaunchDaemons/moodle4mac.cron.plist''. The owner of the file must be set to the system user ''root''. If you use a site with SSL (ie: it has an http'''s''':// protocol) you either need to have your SSL certificates listed for use by the CURL utility ([http://curl.haxx.se/docs/sslcerts.html see these docs] for more details) OR you must use the '-k' switch in addition to the '-s' switch used above; your arguments line would then read: `<string>-s -k</string>`.

That's all, really!

===How to start and stop the cron service===
You can start the new cron service in the Terminal.

sudo launchctl load /Library/LaunchDaemons/moodle4mac.cron.plist

The following command would stop the service. If you want to activate changes in the cron service you need to ''unload'' and then to ''load'' the daemon again.

sudo launchctl unload /Library/LaunchDaemons/moodle4mac.cron.plist

===Only one service for two servers?===
For my server I needed to have a cron service for to instances ''moodle19'' and ''moodle20'' ... no problem ... with the typo ''moodle[19-20]'' I will get a cron service for both.

<nowiki>curl -s http://your-server-address/moodle[19-20]/admin/cron.php</nowiki>

To see if the cron service works correctly you should look at the ''access.log'' of your web server. The cron.php should be accessed every 5 minutes ... on my server for both Moodle instances ''moodle19'' and ''moodle20'' ... oh yes, it works!!

192.168.0.220 - - [30/Jul/2009:22:10:56 +0200] "GET /moodle19/admin/cron.php HTTP/1.1" 200 1136
192.168.0.220 - - [30/Jul/2009:22:10:57 +0200] "GET /moodle20/admin/cron.php HTTP/1.1" 200 1403
192.168.0.220 - - [30/Jul/2009:22:11:18 +0200] "OPTIONS * HTTP/1.0" 200 -
192.168.0.220 - - [30/Jul/2009:22:15:56 +0200] "GET /moodle19/admin/cron.php HTTP/1.1" 200 735
192.168.0.220 - - [30/Jul/2009:22:15:57 +0200] "GET /moodle20/admin/cron.php HTTP/1.1" 200 964
192.168.0.220 - - [30/Jul/2009:22:20:56 +0200] "GET /moodle19/admin/cron.php HTTP/1.1" 200 1136
192.168.0.220 - - [30/Jul/2009:22:20:57 +0200] "GET /moodle20/admin/cron.php HTTP/1.1" 200 1365

==Managing cron on web hosting services==

Your web-based control panel may have a web page that allows you to set up a cron service process.

===CPanel cron service===
If you are using CPanel, login then look for "Advanced" category towards the bottom of the page. Click on Cron Jobs -> Advanced (Unix style). Enter the following for the cron to run every 30 minutes.

Email address for output: emailaddress@mydomain.con
Minute:*/30
Hour:*
Day:*
Month:*
Weekday:*
<nowiki>Command: wget -q -O /dev/null http://www.mydomain.com/moodle/admin/cron.php</nowiki>

Click Commit Changes. Check your email for the output.

[[Image:Cpanel-cron-setup.JPG]]

===Other systems cron service===
For other systems, look for a button called "Cron jobs". In there you can put the same sort of Unix commands as listed below.

If you don't have permissions to run the 'wget' command on the server, you can use this php command:

/usr/local/bin/php -q /real/path/to/script/admin/cron.php

For example:

/usr/local/bin/php -q /home/username/public_html/moodle/admin/cron.php

If you don't know what is the real path of your Moodle folder you can use the PHP command realpath.

Another alternative, if you do not have permission to run the 'wget' command, may be to use a curl command.

For example:

curl --silent --compressed http://mydomain.com/moodle/admin/cron.php

==Using a cron command line in Unix==

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.

'''Note:''' The examples with wget, lynx, and similar are '''not''' the same as the "CLI only" cron checkbox, mentioned above (the configuration variable "cronclionly"). wget, lynx, and other similar utilities are Unix command-line HTTP clients, and thus running cron.php in this way is the same as running it in a browser, from Moodle's point of view.

For example, you can use a Unix utility like 'wget':

wget -q -O /dev/null <nowiki>http://example.com/moodle/admin/cron.php</nowiki>

Note in this example that the output is thrown away (to /dev/null).

A number of users of Moodle have found that 'wget' sometimes fails. Especially if you have trouble with email digests not being sent on a daily basis to all users, an alternative command that solves the problem is:

php <nowiki>http://example.com/moodle/admin/cron.php</nowiki>

The same thing using lynx:

lynx -dump <nowiki>http://example.com/moodle/admin/cron.php</nowiki> > /dev/null

Note in this example that the output is thrown away (to /dev/null).

Alternatively, you can use a standalone version of PHP, compiled to be run on the command line. The disadvantage is that you need to have access to a command-line version of php. The advantage is that your web server logs aren't filled with constant requests to cron.php and you can run at a lower I/O and CPU priority.

/opt/bin/php /web/moodle/admin/cron.php

Example command to run at lower priority:

ionice -c3 -p$$;nice -n 10 /usr/bin/php /moodle/admin/cron.php > /dev/null

===Using the crontab program on Unix===

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:

crontab -e

and then adding one of the above commands like:

*/30 * * * * wget -q -O /dev/null <nowiki>http://example.com/moodle/admin/cron.php</nowiki>

The first five entries are the times to run values, followed by the command to run. The asterisk is a wildcard, indicating any time. The above example means run the command ''wget -q -O /dev/null...'' every 30 minutes (*/30), every hour (*), every day of the month (*), every month (*), every day of the week (*).

The "O" of "-O" is the capital letter not zero, and refers the output file destination, in this case "/dev/null" which is a black hole and discards the output. If you want to see the output of your cron.php then enter its url in your browser.

* [http://linuxweblog.com/node/24 A basic crontab tutorial]
* [http://www.freebsd.org/cgi/man.cgi?query=crontab&apropos=0&sektion=5&manpath=FreeBSD+6.0-RELEASE+and+Ports&format=html Online version of the man page]

For '''beginners''', "EDITOR=nano crontab -e" will allow you to edit the crontab using the [http://www.nano-editor.org/dist/v1.2/faq.html nano] editor. Ubuntu defaults to using the nano editor.

Usually, the "crontab -e" 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 without saving using ":q!" (without the quotes). Here is an [http://www.unix-manuals.com/tutorials/vi/vi-in-10-1.html intro] to the 'vi' editor.

==See also==

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=41827 Cron - can someone give me a quick confirmation of function?]
*[http://moodle.org/mod/forum/discuss.php?d=97684 Cronjob Question]
*[http://moodle.org/mod/forum/discuss.php?d=97457 Slow cron : avoiding simultaneous cron]
*[http://moodle.org/mod/forum/discuss.php?d=117168 Visibility of cron.php]
*[http://moodle.org/mod/forum/discuss.php?d=139263#p609060 How to log the output of a Scheduled Task on Windows] - this discussion explains a nice trick that can be very useful when you are experiencing problems with your Windows Scheduled Task and you need to log the output of the Scheduled Task to a log file.

[[Category:Installation]]

[[es:Cron]]
[[fr:Cron]]
[[nl:Cron]]
[[sk:Cron]]
[[pl:Cron]]
[[ja:Cron]]

LDAP authentication

2010-08-04T17:55:09Z

Matthewm1970: /* User lookup settings */

{{Moodle 1.9}}
Location: Settings link in ''Administration > Users > [[Authentication]] > LDAP Server''

This document describes how to set up Lightweight Directory Access Protocol (LDAP) authentication in Moodle. We cover the basic, advanced and some trouble shooting sections to assist the user in the installation and administrating LDAP in Moodle.
==Table of Contents==
__TOC__
==Basic Scenario==
The simple and straightforward approach for most installations.

===Assumptions===

# Your Moodle site is located at '''http://your.moodle.site/'''
# You have configured your PHP installation with the LDAP extension. It is loaded and activated, and it shows when you go to '''http://your.moodle.site/admin/phpinfo.php''' (logged in as user 'admin').
# Your LDAP server has '''192.168.1.100''' as its IP address.
# You are not using LDAP with SSL (also known as LDAPS) in your settings. This might prevent certain operations from working (e.g., you cannot update data if you are using MS Active Directory -- MS-AD from here on --), but should be OK if you just want to authenticate your users.
# You don't want your users to change their passwords the first time they log in into Moodle.
# You are using a single domain as the source of your authentication data in case you are using MS-AD (more on this in the Appendices).
# You are using a top level distinguished name (DN) of '''dc=my,dc=organization,dc=domain''' as the root of your LDAP tree.
# You have a non-privileged LDAP user account you will use to bind to the LDAP server. This is not necessary with certain LDAP servers, but MS-AD requires this and it won't hurt if you use it even if your LDAP server doesn't need it. Make sure '''this account and its password don't expire''', and make this password as strong as possible. Remember you only need to type this password once, when configuring Moodle, so don't be afraid of making it as hard to guess as possible. Let's say this user account has a DN of '''cn=ldap-user,dc=my,dc=organization,dc=domain''', and password '''hardtoguesspassword'''.
# All of your Moodle users are in an organizational unit (OU) called '''moodleusers''', which is right under your LDAP root. That OU has a DN of '''ou=moodleusers,dc=my,dc=organization,dc=domain'''.
# You '''don't''' want your LDAP users' passwords to be stored in Moodle at all.

[[LDAP_authentication#Table of Contents|Table of Contents]]

===Configuring Moodle authentication===

Log in as an admin user and go to Administration >> Users >> Authentication >> Manage authentication. In the table that appears, enable the "LDAP Server" authentication option (click on the closed eye to make it open) and then click on the associated 'Settings' link. You will get a page similar to this one:

[[Image:auth_ldap_config_screenshot.jpg|center]]

Now, you just have to fill in the values. Let's go step by step.

[[LDAP_authentication#Table of Contents|Table of Contents]]

====LDAP Server Settings====
{| border="1" cellspacing="0" cellpadding="5"
! Field name
! Value to fill in
|-
| Host URL
| As the IP of your LDAP server is 192.168.1.100, type "'''ldap://192.168.1.100'''" (without the quotes), or just "'''192.168.1.100'''" (some people have trouble connecting with the first syntax, specially on MS Windows servers).
|-
| Version
| Unless you are using a really old LDAP server, '''version 3''' is the one you should choose.
|-
| LDAP Encoding
| Specify encoding used by LDAP server. Most probably utf-8.
|}

[[LDAP_authentication#Table of Contents|Table of Contents]]

====Bind settings====
{| border="1" cellspacing="0" cellpadding="5"
! Field name
! Value to fill in
|-
| Hide passwords
| As you '''don't''' want to store the users's password in Moodle's database, choose '''Yes''' here.
|-
| Distinguished Name
| This is the distinguished name of the bind user defined above. Just type "'''cn=ldap-user,dc=my,dc=organization,dc=domain'''" (without the quotes).
|-
| Password
| This is the bind user password defined above. Type "'''hardtoguesspassword'''" (without the quotes).
|}

[[LDAP_authentication#Table of Contents|Table of Contents]]

====User lookup settings====
{| border="1" cellspacing="0" cellpadding="5"
! Field name
! Value to fill in
|-
| User type
| Choose:
* '''Novel Edirectory''' if your LDAP server is running Novell's eDdirectory.
* '''posixAccount (rfc2307)''' if your LDAP server is running a RFC-2307 compatible LDAP server (choose this is your server is running OpenLDAP, including Mac OS X server).
* '''posixAccount (rfc2307bis)''' if your LDAP server is running a RFC-2307bis compatible LDAP server.
* '''sambaSamAccount (v.3.0.7)''' if your LDAP server is running with SAMBA's 3.x LDAP schema extension and you want to use it.
* '''MS ActiveDirectory''' if your LDAP server is running Microsoft's Active Directory (MS-AD)
|-
| Contexts
| The DN of the context (container) where all of your Moodle users are found. Type '''ou=moodleusers,dc=my,dc=organization,dc=domain''' here.

On a Mac OS X Server, this is usually '''cn=users,dc=my,dc=organization,dc=domain'''.
|-
| Search subcontexts
| If you have any sub organizational units (subcontexts) hanging from '''ou=moodleusers,dc=my,dc=organization,dc=domain''' and you want Moodle to search there too, set this to '''yes'''. Otherwise, set this to '''no'''.
|-
| Dereference aliases
| Sometimes your LDAP server will tell you that the real value you are searching for is in fact in another part of the LDAP tree (this is called an alias). If you want Moodle to 'dereference' the alias and fetch the real value from the original location, set this to '''yes'''. If you don't want Moodle to dereference it, set this to '''no'''. If you are using MS-AD, set this to '''no'''.
|-
| User attribute
| The attribute used to name/search users in your LDAP tree. This option takes a default value based on the ''User type'' value you chose above. So unless you need something special, you don't need to fill this in.

By the way, it's usually '''cn''' (Novell eDirectory and MS-AD) or '''uid''' (RFC-2037, RFC-2037bis and SAMBA 3.x LDAP extension), but if you are using MS-AD you could use '''sAMAccountName''' (the pre-Windows 2000 logon account name) if you need too.
|-
| Member attribute
| The attribute used to list the members of a given group. This option takes a default value based on the ''User type'' value you choosed above. So unless you need something special, you don't need to fill this in.

By the way, the usual values are '''member''' and '''memberUid'''.
|-
| Member attribute uses dn
| Whether the member attribute contains distinguished names (1) or not (0).This option takes a default value based on the ''User type'' value you choosed above. So unless you need something special, you don't need to fill this in.
|-
| Object class
| The type of LDAP object used to search for users. This option takes a default value based on the ''User type'' value you chose above. So unless you need something special, you don't need to fill this in.
* If you leave it blank, the filter "(objectClass=*)" will be used.
* If you provide "objectClass=some-string", then it will provide "(objectClass=some-string)" as the filter.
* If you provide a value that does not start with "(", it is assumed to be a value that should be set to "objectClass". So if you provide "some-string", then it will provide "(objectClass=some-string)" as the filter.
* If you provide a string that starts with a "(", then it will pass that as is. So if you provide "(&(objectClass=user)(enabledMoodleUser=1))", then it will pass that as the filter.

Here are the default values for each of the ''ldap_user_type'' values:
* '''User''' for Novel eDirectory
* '''posixAccount''' for RFC-2037 and RFC-2037bis
* '''sambaSamAccount''' for SAMBA 3.0.x LDAP extension
* '''user''' for MS-AD
If you get an error about a problem with updating the ldap server (even if you have specified not to write changes back to the ldap server) try setting the ldap object class to * - see http://moodle.org/mod/forum/discuss.php?d=70566 for a discussion on this problem
|}

[[LDAP_authentication#Table of Contents|Table of Contents]]

====Force change password====
{| border="1" cellspacing="0" cellpadding="5"
! Field name
! Value to fill in
|-
| Force change password
| Set this to ''Yes'' if you want to force your users to change their password on the first login into Moodle. Otherwise, set this to ''no''. Bear in mind the password they are forced to change is the one stored in your LDAP server.

As you don't want your users to change their passwords in their first login, leave this set to ''No''
|-
| Use standard Change Password Page
|
* Setting this to ''Yes'' makes Moodle use it's own standard password change page, everytime users want to change their passwords.
* Setting this to ''No'' makes Moodle use the the page specified in the field called "Password change URL" (see below).

Bear in mind that changing your LDAP passwords from Moodle might require a LDAPS connection (this is actually a requirement for MS-AD). In addition to that, the bind user specified above must have the rights needed to change other users' passwords.

Also, code for changing passwords from Moodle for anything but Novell eDirectory and Active Directory is almost not tested, so this may or may not work for other LDAP servers.
|-
| Password Format
| Specify how the new password is encrypted before sending it to the LDAP server: Plain text, MD5 hash or SHA-1 hash. MS-AD uses plain text, for example.
|-
| Password change URL
| Here you can specify a location at which your users can recover or change their username/password if they've forgotten it. This will be provided to users as a button on the login page and their user page. if you leave this blank the button will not be printed.
|}

[[LDAP_authentication#Table of Contents|Table of Contents]]

====LDAP password expiration settings====
{| border="1" cellspacing="0" cellpadding="5"
! Field name
! Value to fill in
|-
| Expiration
|
* Setting this to ''No'' will make Moodle not to check if the password of the user has expired or not.
* Setting this to ''LDAP'' will make Moodle check if the LDAP password of the user has expired or not, and warn her a number of days before the password expires.

Current code only deals with Novell eDirectory LDAP server and MS-AD.

So unless you have Novell eDirectory server or MS-AD, choose ''No'' here.
|-
| Expiration warning
| This value sets how many days in advance of password expiration the user is warned that her password is about to expire.
|-
| Expiration attribute.
| The LDAP user attribute used to check password expiration. This option takes a default value based on the ''User type'' value you choosed above. So unless you need something special, you don't need to fill this in.
|-
| Grace logins
| This setting is specific to Novell eDirectory. If set to ''Yes'', enable LDAP gracelogin support. After password has expired the user can login until gracelogin count is 0.

So unless you have Novell eDirectory server and want to allow gracelogin support, choose ''No'' here.
|-
| Grace login attribute
| This setting is currently not used in the code (and is specific to Novell eDirectory).

So you don't need to fill this in.
|}

[[LDAP_authentication#Table of Contents|Table of Contents]]

====Enable user creation====
{| border="1" cellspacing="0" cellpadding="5"
! Field name
! Value to fill in
|-
| Create users externally
| New (anonymous) users can self-create user accounts on the external LDAP server and confirm them via email. If you enable this, remember to also configure module-specific options for user creation and to fill in some instructions in ''auth_instructions'' field in Administration >> Users >> Authentication >> Manage authentication. Otherwise the new users won't be able to self-create new accounts.

As of now, only Novell eDirectory and MS-AD can create users externally.
|-
| Context for new users
| Specify the context where users are created. This context should be different from other users' contexts to prevent security issues.
|}

[[LDAP_authentication#Table of Contents|Table of Contents]]

====Course creation====
{| border="1" cellspacing="0" cellpadding="5"
! Field name
! Value to fill in
|-
| Creators
| The DN of the group that contains all of your Moodle creators. This is typically a posixGroup with a "memberUid" attribute for each user you want to be a creator. If your group is called ''creators'', type '''cn=creators,ou=moodleusers,dc=my,dc=organization,dc=domain''' here. Each memberUid attribute contains the CN of a user who is authorized to be a creator. Do not use the user's full DN (e.g., not '''memberUid: cn=JoeTeacher,ou=moodleusers,dc-my,dc=organizations,dc=domain''', but rather '''memberUid: JoeTeacher''').

In eDirectory, the objectClass for a group is (by default) not '''posixGroup''' but '''groupOfNames,''' whose member attribute is '''member,''' not '''memberUid,''' and whose value is the full DN of the user in question. Although you can probably modify Moodle's code to use this field, a better solution is just to add a new '''objectClass''' attribute of '''posixGroup''' to your creators group and put the CNs for each creator in a '''memberUid''' attribute.

In MS Active Directory, you will need to create a security group for your creators to be part of and then add them all. If your ldap context above is 'ou=staff,dc=my,dc=org' then your group should then be 'cn=creators,ou=staff,dc=my,dc=org'. If some of the users are from other contexts and have been added to the same security group, you'll have to add these as separate contexts after the first one using the same format.
|}

[[LDAP_authentication#Table of Contents|Table of Contents]]

====Cron synchronization script====
{| border="1" cellspacing="0" cellpadding="5"
! Field name
! Value to fill in
|-
| Removed ext user
| Specify what to do with internal user account during mass synchronization when user was removed from external source. Only suspended users are automatically revived if they reappear in ext source.
|}

[[LDAP_authentication#Table of Contents|Table of Contents]]

====NTLM SSO====
{| border="1" cellspacing="0" cellpadding="5"
! Field name
! Value to fill in
|-
| Enable
| If you want to use NTLM SSO (see details at [[NTLM_authentication]]), choose ''Yes'' here. Otherwise, choose ''No''.
|-
| Subnet
| Specify the subnets of the clients that will use NTLM SSO (see details at [[NTLM_authentication]]).
|-
| MS IE Fast Path?
| If all of you clients (or most of them) are using MS Internet Explorer, you can set this option to bypasses certain steps of the SSO login and speed up login times. This only works with MS Internet Explorer, but deals with other browsers in a sensible way (they are automatically sent to the plain login page).
|}

[[LDAP_authentication#Table of Contents|Table of Contents]]

====Data Mapping====
{| border="1" cellspacing="0" cellpadding="5"
! Field name
! Value to fill in
|-
| First name
| The name of the attribute that holds the first name of your users in your LDAP server. This is usually '''givenName''' or '''displayName'''

This setting is optional
|-
| Surname
| The name of the attribute that holds the surname of your users in your LDAP server. This is usually '''sn'''.

This setting is optional
|-
| Email address
| The name of the attribute that holds the email address of your users in your LDAP server. This is usually '''mail'''.

This setting is optional
|-
| City/town
| The name of the attribute that holds the city/town of your users in your LDAP server. This is usully '''l''' (lowercase L) or '''localityName''' (not valid in MS-AD).

This setting is optional
|-
| Country
| The name of the attribute that holds the country of your users in your LDAP server. This is usully '''c''' or '''countryName''' (not valid in MS-AD).

This setting is optional
|-
| Language
| '''preferredLanguage'''

This setting is optional
|-
| Description
| '''description'''

This setting is optional
|-
| Webpage
| This setting is optional
|-
| ID Number
|

This setting is optional
|-
| Institution
|

This setting is optional
|-
| Department
| The name of the attribute that holds the department name of your users in your LDAP server. This is usully '''departmentNumber''' (for posixAccount and maybe eDirectory) or '''department''' (for MS-AD).

This setting is optional
|-
| Phone 1
| The name of the attribute that holds the telephone number of your users in your LDAP server. This is usually '''telephoneNumber'''.

This setting is optional
|-
| Phone 2
| The name of the attribute that holds an additional telephone number of your users in your LDAP server. This can be '''homePhone''', '''mobile''', '''pager''', '''facsimileTelephoneNumber''' or even others.

This setting is optional
|-
| Address
| The name of the attribute that holds the street address of your users in your LDAP server. This is usully '''streetAddress''' or '''street'.

This setting is optional
|}

[[LDAP_authentication#Table of Contents|Table of Contents]]

===Setting up regular automatic synchronisation using cron===
There is a script located at /auth/ldap/auth_ldap_sync_users.php which will create or suspend/delete (see the setting above) all LDAP accounts automatically. Ideally, this is called from the command line once a day during a quiet time using exactly the same procedure as the standard [[Cron|cron]] job (so you will end up with two cron entries). It is important, however, to make sure that all of the above LDAP settings are working properly before you try this, as well as backing up your database and moodledata folders. Poor LDAP configuration could lead to users being wrongly deleted.

If you find that the script is not running through all of your users properly and you have MS Active Directory + over 1000 users, this is because by default, MS AD only sends back 1000 users at a time. Follow the instructions [http://support.microsoft.com/kb/315071 here] to set the MaxPageSize setting to a number higher than your total number of users (both now and in future) to fix it.

[[LDAP_authentication#Table of Contents|Table of Contents]]

==Active Directory help==
[[Active Directory]] is Microsoft's directory service. It is included in Windows 2000 Server and later versions of their operating system. For more information about subjects below, '''[[Active Directory|please go here]]'''.

*Warning: The PHP LDAP module does not seem to be present
*LDAP-module cannot connect any LDAP servers
*Getting correct CNs for Contexts and Creators
*Getting the right user_attribute
*Installing ldp.exe Server Tool
*Example Active Directory Configuration
*Child Domains and the Global Catalog in MS Active Directory
*Enabling the Global Catalog
*Active Directory with Moodle 1.8
*MS Active Directory + SSL

==Advanced Scenarios - Multiple servers or locations==
For larger installations with multiple LDAP servers, or multiple locations (contexts) in a LDAP tree.

===Using multiple LDAP Servers===
Entering more than one name in the ldap_host_url field can provide some sort of resilience to your system. Simply use the syntax :
ldap://my.first.server ; ldap://my.second.server ; ...

Of course, this will only work if all the servers share the same directory information, using a replication or synchronization mecanism once introduced in eDirectory and now generalized to the main LDAP-compatible directories.

There is one drawback in Moodle 1.5 - 1.6 implementation of LDAP authentication : the auth_ldap_connect() function processes the servers sequentially, not in a round robin mode. Thus, if the primary server fails, you will have to wait for the connection to time out before switching to the following one.

===Using multiple user locations (contexts) in your LDAP tree===
There is no need to use multiple user locations if your directory tree is flat, i.e. if all user accounts reside in a '''ou=people,dc=my,dc=organization,dc=domain''' or '''ou=people,o=myorg''' container.

At the opposite, if you use the ACL mecanism to delegate user management, there are chances that your users will be stored in containers like '''ou=students,ou=dept1,o=myorg''' and '''ou=students,ou=dept2,o=myorg''' ...

Then there is an alternative :
* Look at the '''o=myorg''' level with the ldap_search_sub attribute set to '''yes'''.
* Set the ldap_context to '''ou=students,ou=dept1,o=myorg ; ou=students,ou=dept2,o=myorg'''.

Choosing between these two solutions supposes some sort of benchmarking, as the result depends heavily on the structure of your directory tree '''and''' on your LDAP software indexing capabilities. Simply note that there is a probability in such deep trees that two users share the same ''common name'' (cn), while having different ''distinguished names''. Then only the second solution will have a deterministic result (returning allways the same user).

===Using LDAPS (LDAP + SSL)===
====Enabling LDAPS on the LDAP server side====

* [[Active_Directory#MS_Active_Directory_.2B_SSL|Enabling LDAPS on MS Active Directory ]]

====Enabling LDAPS on the client side (Moodle server)====

* If you are running Moodle on MS Windows, you need to tell PHP's OpenLDAP extension to disable SSL server certificate checking. You must create a directory called ''C:\OpenLDAP\sysconf''. In this directory, create a file called ''ldap.conf'' with the following content (If you are using certain versions of PHP 5.3.x you may need to place the file at other locations, [http://bugs.php.net/bug.php?id=48866 see PHP bug #48866]):

TLS_REQCERT never

* If you are running Moodle on Linux or any other Unix-like operating system, and you want to disable SSL server certificate checking, you need to edit the OpenLDAP client configuration file (usually /etc/ldap.conf or /etc/ldap/ldap.conf or even /etc/openldap/ldap.conf) and make sure you have a line like the following one:

TLS_REQCERT never

Now you should be able to use '''ldaps://''' when connecting to your LDAP server.

If you have the certificate of the LDAPS server as a file and want to check the certificate for the connection, copy the certificate file to an arbitary directory (e.g. /etc/ldap/certificate.pem) on your client and change the content of the ''ldap.conf'' as follows:

TLS_REQCERT demand
TLS_CACERT /etc/ldap/certificate.pem

When the requested server certificate is bad or not provided, the connection to the LDAPS server is immediately terminated.

[[LDAP_authentication#Table of Contents|Table of Contents]]

==Appendices==
===ldap auth_user_create() only suports Novell===

After configuring user authentication with ldap I realized ldap only support edir (Novell) when combining ldap an email user confirmation. For example in my case (I use openldap) I have the following error after filling the user form:

auth: ldap auth_user_create() does not support selected usertype:"rfc2307" (..yet)

=== Setting Resource Limits RedHat Directory Server ===

Operational attributes can be set for the bind user DN using the command-line.
One can simply use ldapmodify to add the following attributes:

{| border="1" cellspacing="0" cellpadding="5"
! Attribute Name
! Description
|-
| nsLookThroughLimit
| Specifies how many entries are examined for a search operation. Giving this attribute a value of -1 indicates that there is no limit.
|-
| nsSizeLimit
| Specifies the maximum number of entries the server returns to a client application in response to a search operation. Giving this attribute a value of -1 indicates that there is no limit.
|-
| nsTimeLimit
| Specifies the maximum time the server spends processing a search operation. Giving this attribute a value of -1 indicates that there is no time limit.
|-
| nsIdleTimeout
| Specifies the time a connection to the server can be idle before the connection is dropped. The value is given in seconds. Giving this attribute a value of -1 indicates that there is no limit.
|}

<pre> LDAP Console Command-Line

ldapmodify -h redhat_dir_server -p 389 -D "cn=directory manager" -w secretpwd

dn: uid=MoodleAdmin,ou=system,dc=myschool,dc=edu
changetype: modify
add:nsSizeLimit
nsSizeLimit: 1000
</pre>

[[LDAP_authentication#Table of Contents|Table of Contents]]

==See also==

* [[NTLM_authentication]]
* [[Active_Directory]]
* [[LDAP enrolment]]
* [http://download.moodle.org/download.php/docs/en/how-to_guides/ldap_auth_and_enrolment_set-up.pdf LDAP auth and enrolment set-up guide] (PDF 227KB)

Using Moodle:
* [http://moodle.org/mod/forum/view.php?id=42 User authentication forum]
* [http://moodle.org/mod/forum/discuss.php?d=32168 PHP LDAP module does not seem to be present] forum discussion
* [http://moodle.org/mod/forum/discuss.php?d=140901 Syncronisation with AUTH_LDAP_SYNC_USERS.PHP produces fewer accounts than it should] forum discussion
* [http://moodle.org/mod/forum/discuss.php?d=17198 Using multiple LDAP servers] forum discussion

[[Category:Authentication]]

[[es:LDAP_authentication]]
[[fr:Utiliser un serveur LDAP]]
[[ja:LDAP認証]]
[[zh:LDAP认证]]
[[de:Authentifizierung über LDAP]]

Step by Step Installation on a Mac OS X 10.5 Server

2010-06-17T17:31:41Z

Matthewm1970:

==Overview==
This guide shows all steps for the installation of Moodle on a [http://www.apple.com/server/macosx Mac OS X 10.5 Server]. This server is a commercial product.

This installation guide can't be useful for an installation on MAMP or XAMPP. If you are looking for an easy way to install Moodle on your local machine please use [[Complete Install Packages for Mac OS X | Complete install packages for Mac OS X 10.4/10.5]] that can be downloaded from http://download.moodle.org/macosx/ ... but if you are planning to set up a Moodle internet server on a Mac then you should think about some more security as the ever local package could give.

Please feel free to add your ideas and wishes to the discussion page for this article. You may also write a complete chapter if you tried the facts yourself on your own Mac Server. I am most interested in the "user administration via LDAP" and I hope to get enough ideas how to get all Mac users into the Moodle user list automaticly.

==System requirements==

+ Apple Computer
+ Mac mini, Mac Pro or Xserve
+ Processor: Intel Core 2 Duo
+ RAM: 2 GB or better
+ Hard Disk: 500 MB free
+ System Software: Mac OS X 10.5 Server

==Install PHP 5.3.0 and the GD Library on the Mac OS X 10.5 Server==

<div style="background-color: yellow; padding: 5px;">Note: If you want to install Moodle 1.8.x on the server you need to get the Entropy PHP-5.2.9-7.pkg for the following steps. Moodle 1.8.9 does not run with PHP 5.3.0 in this moment. All the other things should work in the same way for all Moodle versions.</div>

The Mac OS X Server 10.5.6 Leopard comes with PHP 5.2.6 ... this is correct for Moodle 1.9.x. But you have to add the missing GD Library support to get Moodle running on your server. For Moodle 2.0 the server needs PHP 5.2.8 (or better) and some more PHP extensions ... in this case you must get a better PHP version. These instructions are helpful in both cases.

To see which PHP version and extensions are installed on your server you should edit the file ''/Library/WebServer/Documents/info.php''. You must activate the function call phpinfo() by deleting the both slashes // at the start of the function line. After saving the file you can get all PHP informations in your browser. Please look at http://your-server-address/info.php ... you will not find any GD library support ... bad thing for Moodle!!

<?php
// You can use Server Admin to enable the Apache PHP module; it's disabled by default.
// You can uncomment the phpinfo() directive below to provide a default PHP info page
// but note that this displays information about your host's configuration.
phpinfo();
?>

The easiest way to get the GD library support and to get a better PHP version would be the installation of the complete PHP 5.3.0 package from http://www.entropy.ch/software/macosx/php/. Marc Liyanage precompiled this package to use it on Mac clients and Mac servers. Please get the package and install it by following the instructions on the download page. The installer does everything for you ... it copies PHP into the correct folder ''/usr/local/php5'' and changes its owner to ''root'' automatically.

Now the Apache web server must get knowledge that you want to use the new PHP library instead of the old. Open the application Server Admin to switch to the new library. Go to the web server settings and find the entry php5_module. The normal place for PHP the Mac server is ''libexec/apache2/libphp5.so''. Please change to ''/usr/local/php5/libphp5.so'' and save the settings.

[[Image:Server-admin.png]]

The second thing to configure is the file php.ini. You will find this file inside the new package folder. Open the file ''/usr/local/php5/lib/php.ini'' and edit some settings for Moodle. Most of the settings are okay but not all of them. To communicate to the MySQL database with PHP you have to set the default socket name for local MySQL connects. The default socket name for local MySQLi connects is needed for Moodle 2.0.

If you want to upload any file to your Moodle you should add a little bit more upload size in php.ini. If your server can't use more than 1 GB RAM you should set the memory_limit to a value less than 128M ... but it should have more than 48M for Moodle 1.9 and Moodle 2.0. Note that these sections are not likely to be consecutive in the php.ini file; the quickest way to find each one is search on the initial term (such as 'mysql.default_socket').

; Default socket name for local MySQL connects.
; If empty, uses the built-in MySQL defaults.
mysql.default_socket = /var/mysql/mysql.sock

; Default socket name for local MySQL connects.
; If empty, uses the built-in MySQL defaults.
mysqli.default_socket = /var/mysql/mysql.sock

; Maximum amount of memory a script may consume (128MB)
memory_limit = 128M

; Maximum allowed size for uploaded files.
upload_max_filesize = 128M

; Maximum size of POST data that PHP will accept.
post_max_size = 128M

That's all ... save the file php.ini and restart the web server. Now you should look at http://your-server-address/info.php again. I hope that everything will be okay. You will find the version number PHP 5.3.0 and the running GD library support. Congratulations ... the first step for Moodle on the Mac server is done!

[[Image:phpinfo.png]]

[[Image:phpinfo2.png]]

==Configure the MySQL database for your Moodle installation==

In standard case the database MySQL is installed on the Mac OS X 10.5 Server but it is not running yet. Please make sure that you start the MySQL database server.

===Use the graphical way===
Sorry ... there are some more installations and a lot of clicks to configure MySQL in a graphical way.

First of all start the ''Server Admin''. You will find this program by the way ''Applications > Server > Server Admin''. Activate MySQL on the local server. You must set the password for the user ''root'' before you can start MySQL.

For the next you must download the MySQL database administration tool '''phpMyAdmin''' from http://www.phpmyadmin.net . Move the folder to the web server documents as ''/Library/WebServer/Documents/phpMyAdmin''.

Add the security phrase to the file ''config.inc.php'' in between the single quotes on the line $cfg['blowfish_secret'] = ''; /* YOU MUST FILL IN THIS FOR COOKIE AUTH! */

Now you will be able to start http://your-server-address/phpMyAdmin/ in your browser and to log into the database as the user ''root''. Add a database ''moodle19''. Add a database user ''moodle'' to the server ''localhost''. Don't forget to set a secure password. The database user ''moodle'' should be allowed to administrate the database ''moodle19'' only. It is a bad way to set ''root'' to administrate the database ''moodle19''. If you want to install also Moodle 2.0 dev please add a second database ''moodle20'' and use the same database user for it.

phpMyAdmin is a nice thing to look into the database while Moodle is running for some time. It's much easier to see in the graphical interface than in the command line tools. The image shows the database after Moodle 1.9 and Moodle 2.0 were already installed on this server.

[[Image:phpmyadmin.png]]

===Use the Terminal===
If you want a quick installation then don't fear to use the Terminal. It's easier to tell you all the commands for the right way with the Terminal than showing you all the pictures to do the same with graphical tools. There are only a few commands to do everything I told you before.

Start the Terminal. You will find this program by the way ''Applications > Tools > Terminal''. You will see that we must do the same steps as before but you can read them in a text form.

First of all you need to set the root password. If you didn't this before then use the first command line. If you want to change an existing password then use the second one.

Server:~ $ mysqladmin -u root password 'secret'
Server:~ $ mysqladmin -u root -p password 'topsecret'

The next steps are creating a new database ''moodle19'' with correct character set and setting up a database user ''moodle'', with an assigned password (IDENTIFIED BY), to administrate the new database ... and if you want, then do the same for ''moodle20''.

Server:~ $ mysqladmin -u root -p create moodle19
Server:~ $ mysql -u root -p

mysql> ALTER DATABASE moodle19 CHARSET 'utf8';
mysql> GRANT ALL PRIVILEGES ON moodle19.* TO moodle@localhost
-> IDENTIFIED BY 'moodle!';
mysql> quit

Server:~ $

That's really all with the Terminal. You are just ready!

==Copy the Moodle files to the web server==

The documents for the web server are saved in the folder ''/Library/WebServer/Documents/''. You will place your Moodle folder here after you got it from http://download.moodle.org. Download the standard package MOODLE_19_WEEKLY because this is the best choice for new servers. Set the owner ''_www'' for the moodle folder ... this is the user for the web server. The folder permissions should be 755 before the installation and 555 after it's done ... please remember to set this later!

You also need the moodledata folder outside of the Documents folder ... so please make one. Go to the folder ''/Library/WebServer/'' and add the folder ''moodledata''. Because I want to install Moodle 1.9.x and Moodle 2.0 dev together on the same Mac server I add two folders ''moodle19'' and ''moodle20'' inside the moodledata folder. Please set the owner ''_www'' for both folders ''moodle19'' and ''moodle20'' and the folder permissions to 755.

cd /Library/WebServer/
mkdir moodledata
mkdir moodledata/moodle19
mkdir moodledata/moodle20
sudo chown -R _www moodledata
sudo chmod -R 755 moodledata

If you'd like to put the moodledata folder on another volume (not a bad idea if you think you'll have a substantial amount of data within the moodle), note that you cannot simply reference it using the /Volumes/<volume_name>/folder syntax during the moodle setup. Instead, you'll need to create the folder (assigning the user and permissions), then create a '''link''' to it within the /Library/WebServer folder. To create the link, use the following command in a terminal window, substituting your data volume and folder name:

cd /Library/WebServer
ln -s /Volumes/Data_Volume/moodledata moodledata

==Run the Moodle installation==
The installation on the Mac server is the same like the installation on every other server.
Open a web browser to http://your-server-address/moodle/install.php to begin the installation process.
On the screen picture and in the shown config.php you see the web address ''your-server-address'' ... it's only a placeholder for a real address or url ... please set yours. Also a user 'moodle' with a password 'moodle' would be very unsafe settings for your installation.

[[Image:moodle-install1.png]]

[[Image:moodle-install2.png]]

The installer generates the config.php automatically and saves it in the folder ''/Library/WebServer/Documents/moodle19''. Please edit the config.php with a text editor and add the line ''date_default_timezone_set('UTC');''. You may change ''UTC'' to your own timezone ... this is needed for PHP 5.3.0. In case you don't know all the relevant time zone identifiers by heart, there is a [http://phpbuilder.com/manual/en/timezones.php list available online].

<?php /// Moodle Configuration File

unset($CFG);

$CFG->dbtype = 'mysql';
$CFG->dbhost = 'localhost';
$CFG->dbname = 'moodle19';
$CFG->dbuser = 'moodle';
$CFG->dbpass = 'moodle';
$CFG->dbpersist = false;
$CFG->prefix = 'mdl_';

$CFG->wwwroot = 'http://your-server-address/moodle19';
$CFG->dirroot = '/Library/WebServer/Documents/moodle19';
$CFG->dataroot = '/Library/WebServer/moodledata/moodle19';
$CFG->admin = 'admin';

$CFG->directorypermissions = 00777; // try 02777 on a server in Safe Mode

date_default_timezone_set('Europe/Berlin'); // timezone for PHP 5.3.0
require_once("$CFG->dirroot/lib/setup.php");
// MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,
// RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.
?>

After this, the web-based installation component will walk you through '''several''' screens worth of database configurations and updates, for most of which you'll just click the continue button. You'll set up an admin user and give the site a basic configuration (title, description, etc). When the installation is ready you should change the folder permission for ''/Library/WebServer/Documents/moodle19'' to 555 so the web server is not able to write into this folder again.

==Download the language packages==

==Moodle is running ...==
[[Image:moodle-on-macosx-server.png]]

==How to setup the cron job with launchd==

It's really important to start the cron job every 5 minutes. The cron job assists most of Moodle's modules to perform tasks on a scheduled basis. For example, the discussion forums can only mail out copies of new posts to all subscribers if the cron job tells Moodle to do this.

In Mac OS X 10.5 you will find the system daemon ''launchd'' for this service. This daemon offers a standardized interface to any user and all programs started automatically by the system. Please look at http://developer.apple.com/macosx/launchd.html for more information about the configurations and all parameters.

In our case the service should get the web page http://your-server-address/moodle19/admin/cron.php every 5 minutes. The configuration will be done by the file named ''moodle4mac.cron.plist'' which must be placed in the system folder ''/Library/LaunchDaemons/'' ... surely you can use any other file name but it should say something about the function of the service. The extension must be ''.plist''. After any reboot of your Mac server the cron service will start automaticly because the file is placed in the correct system folder.

===Use the graphical way===
You can use Lingon to add a new daemon plist or to edit one. It produces the same text as you can write in your text editor. http://sourceforge.net/projects/lingon/files/

[[Image:macosx-lingon.png]]

===Use a text editor===
Please use a text editor to write the needed file. You can open the Terminal and use the system editors vi or pico. But you can also write the text file with any GUI text editor ... I mostly use TextWrangler ... but do NOT take an editor for formatted texts like Microsoft Word or OpenOffice Writer. You must get pure text!

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>KeepAlive</key><false/>
<key>Label</key><string>moodle4mac.cron</string>
<key>ProgramArguments</key>
<array>
<string>curl</string>
<string>-s</string>
<string>http://your-server-address/moodle19/admin/cron.php</string>
</array>
<key>RunAtLoad</key><true />
<key>StartInterval</key><integer>300</integer>
<key>StandardErrorPath</key><string>/dev/null</string>
<key>StandardOutPath</key><string>/dev/null</string>
</dict>
</plist>

The label string must be the same as the file name is but without the extension ''.plist''. Save the text file ''/Library/LaunchDaemons/moodle4mac.cron.plist''. The owner of the file must be set to the system user ''root''. That's all, really!

===How to start and stop the cron service===
You can start the new cron service in the Terminal.

sudo launchctl load /Library/LaunchDaemons/moodle4mac.cron.plist

The following command would stop the service. If you want to activate changes in the cron service you need to ''unload'' and then to ''load'' the daemon again.

sudo launchctl unload /Library/LaunchDaemons/moodle4mac.cron.plist

===Only one service for two servers?===
For my server I needed to have a cron service for to instances ''moodle19'' and ''moodle20'' ... no problem ... with the typo ''moodle[19-20]'' the server will get a cron service for both instances.

<nowiki>curl -s http://your-server-address/moodle[19-20]/admin/cron.php</nowiki>

To see if the cron service works correctly you should look at the ''access.log'' of your web server. The cron.php should be accessed every 5 minutes ... on my server for both Moodle instances ''moodle19'' and ''moodle20'' ... oh yes, it works!!

192.168.0.220 - - [30/Jul/2009:22:10:56 +0200] "GET /moodle19/admin/cron.php HTTP/1.1" 200 1136
192.168.0.220 - - [30/Jul/2009:22:10:57 +0200] "GET /moodle20/admin/cron.php HTTP/1.1" 200 1403
192.168.0.220 - - [30/Jul/2009:22:11:18 +0200] "OPTIONS * HTTP/1.0" 200 -
192.168.0.220 - - [30/Jul/2009:22:15:56 +0200] "GET /moodle19/admin/cron.php HTTP/1.1" 200 735
192.168.0.220 - - [30/Jul/2009:22:15:57 +0200] "GET /moodle20/admin/cron.php HTTP/1.1" 200 964
192.168.0.220 - - [30/Jul/2009:22:20:56 +0200] "GET /moodle19/admin/cron.php HTTP/1.1" 200 1136
192.168.0.220 - - [30/Jul/2009:22:20:57 +0200] "GET /moodle20/admin/cron.php HTTP/1.1" 200 1365

==How to set up SSL/https in MAMP for a development/test environment==
Following are the steps that I copied from [http://www.webopius.com/content/355/getting-mamp-working-with-ssl-on-os-x webopius web site] (excepted the last steps).
#stop MAMP
#backup your /Applications/MAMP/conf folder
#open a terminal
#enter: ''openssl genrsa -des3 -out server.key 1024''. Enter a password twice.
#enter: ''openssl req -new -key server.key -out server.csr''. Enter the previous password. You need to answer some questions. ''Common name'' expects your local name (for me it was jerome.moodle.local)
#enter: ''openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt''
#enter: ''cp server.key server.tmp''
#enter: ''openssl rsa -in server.tmp -out server.key''. Enter the previous password.
#enter: ''mkdir /Applications/MAMP/conf/ssl''
#enter: cp server.crt /Applications/MAMP/conf/ssl
#enter: cp server.key /Applications/MAMP/conf/ssl
# Edit Applications/MAMP/conf/apache/ssl.conf:
##comment <IfDefine SSL> tag to closing tag (but not the content)
##SSLCertificateFile /Applications/MAMP/conf/ssl/server.crt
##SSLCertificateKeyFile /Applications/MAMP/conf/ssl/server.key
# Edit /Applications/MAMP/conf/apache/httpd.conf:
##Listen 80
##comment <IfDefine SSL> tag to closing tag (but not the content)
# Edit /Application/MAMP/conf/apache/ssl.conf, change the document root (DocumentRoot) for the one you have into /Application/MAMP/conf/apache/httpd.conf
#in a terminal enter: ''cd /Applications/MAMP/bin/apache2/bin''
#enter: ''sudo ./apachectl startssl''
#start MAMP

From now MAMP should start/stop with the SSL support activated. Note that these steps have only be tested with Apache port set to 80 into MAMP preferences.

==How to update with CVS==

==User administration via LDAP==

The following settings will work on 10.5 Server running LDAP - edit them to customize to your own environment. Please note that moodle requires some fields - it is best to have these fields completed in Workgroup Manager on 10.5 Server - otherwise they'll be prompted to enter info into their moodle profile on first login, but the way we've got it set up, moodle can't modify LDAP for security and data integrity. The necessary fields are user name, first name, surname, Email address, City/Town, country, description, ID number.

LDAP SERVER SETTINGS
Host URL = ourserver.example.com
Version = 3
LDAP encoding = utf-8

BIND SETTINGS
Hide passwords = Yes
Distinguished Name = (blank)
Password = (blank)

USER LOOKUP SETTINGS
User type = posixAccount (rfc2307)
Contexts = cn=users,dc=ourserver,dc=example,dc=com
Search subcontexts = Yes
Dereference aliases = No
User attribute = (blank)
Member attribute = (blank)
Member attribute uses dn = (blank)
Object class = (blank)

FORCE CHANGE PASSWORD
Force change password = No
Use standard Change Password Page = No
Password format = Plain text
Password change URL = (blank)

LDAP PASSWORD EXPIRATION SETTINGS
Expiration = no
Expiration warning = 10
Expiration attribute = ""
Grace logins = No
Grace login attribute = (blank)

ENABLE USER CREATION
Create users externally = No
Context for new users = (blank)

COURSE CREATOR
Creators = (blank)

CRON SYNCHRONIZATION SCRIPT
Removed ext user = Keep internal

NTLM SSO
Enable = No
Subnet = (blank)
First name = givenName (On every login, Never, Locked)
Surname = sn (On every login, Never, Locked)
Email address = mail (On every login, Never, Locked)
Phone 1 = (blank)
Phone 2 = (blank)
Department = (blank)
Address = (blank)
City/Town = l (On every login, Never, Locked)
Country = c (On every login, Never, Locked)
Description = description (On every login, Never, Locked)
ID number = uidNumber (On every login, Never, Locked)
Language = (blank)

==See also==
* [[Complete Install Packages for Mac OS X | Complete install packages for Mac OS X 10.4/10.5]]
* [[Step-by-step Guide for Installing Moodle on Mac OS X 10.4 Client|Step by step installation on a Mac OS X 10.4 Client]]
* [[Cron | Installation of cron for Moodle]]
* [[CVS for Administrators]]

* [http://moodle.org/mod/forum/discuss.php?d=24632 Using Moodle: Dynamic DNS Home Server]

[[Category:Administrator]]
[[Category:Installation]]
[[Category:Mac OS X]]

Step by Step Installation on a Mac OS X 10.5 Server

2010-06-17T17:21:56Z

Matthewm1970:

==Overview==
This guide shows all steps for the installation of Moodle on a [http://www.apple.com/server/macosx Mac OS X 10.5 Server]. This server is a commercial product.

This installation guide can't be useful for an installation on MAMP or XAMPP. If you are looking for an easy way to install Moodle on your local machine please use [[Complete Install Packages for Mac OS X | Complete install packages for Mac OS X 10.4/10.5]] that can be downloaded from http://download.moodle.org/macosx/ ... but if you are planning to set up a Moodle internet server on a Mac then you should think about some more security as the ever local package could give.

Please feel free to add your ideas and wishes to the discussion page for this article. You may also write a complete chapter if you tried the facts yourself on your own Mac Server. I am most interested in the "user administration via LDAP" and I hope to get enough ideas how to get all Mac users into the Moodle user list automaticly.

==System requirements==

+ Apple Computer
+ Mac mini, Mac Pro or Xserve
+ Processor: Intel Core 2 Duo
+ RAM: 2 GB or better
+ Hard Disk: 500 MB free
+ System Software: Mac OS X 10.5 Server

==Install PHP 5.3.0 and the GD Library on the Mac OS X 10.5 Server==

<div style="background-color: yellow; padding: 5px;">Note: If you want to install Moodle 1.8.x on the server you need to get the Entropy PHP-5.2.9-7.pkg for the following steps. Moodle 1.8.9 does not run with PHP 5.3.0 in this moment. All the other things should work in the same way for all Moodle versions.</div>

The Mac OS X Server 10.5.6 Leopard comes with PHP 5.2.6 ... this is correct for Moodle 1.9.x. But you have to add the missing GD Library support to get Moodle running on your server. For Moodle 2.0 the server needs PHP 5.2.8 (or better) and some more PHP extensions ... in this case you must get a better PHP version. These instructions are helpful in both cases.

To see which PHP version and extensions are installed on your server you should edit the file ''/Library/WebServer/Documents/info.php''. You must activate the function call phpinfo() by deleting the both slashes // at the start of the function line. After saving the file you can get all PHP informations in your browser. Please look at http://your-server-address/info.php ... you will not find any GD library support ... bad thing for Moodle!!

<?php
// You can use Server Admin to enable the Apache PHP module; it's disabled by default.
// You can uncomment the phpinfo() directive below to provide a default PHP info page
// but note that this displays information about your host's configuration.
phpinfo();
?>

The easiest way to get the GD library support and to get a better PHP version would be the installation of the complete PHP 5.3.0 package from http://www.entropy.ch/software/macosx/php/. Marc Liyanage precompiled this package to use it on Mac clients and Mac servers. Please get the package and install it by following the instructions on the download page. The installer does everything for you ... it copies PHP into the correct folder ''/usr/local/php5'' and changes its owner to ''root'' automatically.

Now the Apache web server must get knowledge that you want to use the new PHP library instead of the old. Open the application Server Admin to switch to the new library. Go to the web server settings and find the entry php5_module. The normal place for PHP the Mac server is ''libexec/apache2/libphp5.so''. Please change to ''/usr/local/php5/libphp5.so'' and save the settings.

[[Image:Server-admin.png]]

The second thing to configure is the file php.ini. You will find this file inside the new package folder. Open the file ''/usr/local/php5/lib/php.ini'' and edit some settings for Moodle. Most of the settings are okay but not all of them. To communicate to the MySQL database with PHP you have to set the default socket name for local MySQL connects. The default socket name for local MySQLi connects is needed for Moodle 2.0.

If you want to upload any file to your Moodle you should add a little bit more upload size in php.ini. If your server can't use more than 1 GB RAM you should set the memory_limit to a value less than 128M ... but it should have more than 48M for Moodle 1.9 and Moodle 2.0. Note that these sections are not likely to be consecutive in the php.ini file; the quickest way to find each one is search on the initial term (such as 'mysql.default_socket').

; Default socket name for local MySQL connects.
; If empty, uses the built-in MySQL defaults.
mysql.default_socket = /var/mysql/mysql.sock

; Default socket name for local MySQL connects.
; If empty, uses the built-in MySQL defaults.
mysqli.default_socket = /var/mysql/mysql.sock

; Maximum amount of memory a script may consume (128MB)
memory_limit = 128M

; Maximum allowed size for uploaded files.
upload_max_filesize = 128M

; Maximum size of POST data that PHP will accept.
post_max_size = 128M

That's all ... save the file php.ini and restart the web server. Now you should look at http://your-server-address/info.php again. I hope that everything will be okay. You will find the version number PHP 5.3.0 and the running GD library support. Congratulations ... the first step for Moodle on the Mac server is done!

[[Image:phpinfo.png]]

[[Image:phpinfo2.png]]

==Configure the MySQL database for your Moodle installation==

In standard case the database MySQL is installed on the Mac OS X 10.5 Server but it is not running yet. Please make sure that you start the MySQL database server.

===Use the graphical way===
Sorry ... there are some more installations and a lot of clicks to configure MySQL in a graphical way.

First of all start the ''Server Admin''. You will find this program by the way ''Applications > Server > Server Admin''. Activate MySQL on the local server. You must set the password for the user ''root'' before you can start MySQL.

For the next you must download the MySQL database administration tool '''phpMyAdmin''' from http://www.phpmyadmin.net . Move the folder to the web server documents as ''/Library/WebServer/Documents/phpMyAdmin''.

Add the security phrase to the file ''config.inc.php'' in between the single quotes on the line $cfg['blowfish_secret'] = ''; /* YOU MUST FILL IN THIS FOR COOKIE AUTH! */

Now you will be able to start http://your-server-address/phpMyAdmin/ in your browser and to log into the database as the user ''root''. Add a database ''moodle19''. Add a database user ''moodle'' to the server ''localhost''. Don't forget to set a secure password. The database user ''moodle'' should be allowed to administrate the database ''moodle19'' only. It is a bad way to set ''root'' to administrate the database ''moodle19''. If you want to install also Moodle 2.0 dev please add a second database ''moodle20'' and use the same database user for it.

phpMyAdmin is a nice thing to look into the database while Moodle is running for some time. It's much easier to see in the graphical interface than in the command line tools. The image shows the database after Moodle 1.9 and Moodle 2.0 were already installed on this server.

[[Image:phpmyadmin.png]]

===Use the Terminal===
If you want a quick installation then don't fear to use the Terminal. It's easier to tell you all the commands for the right way with the Terminal than showing you all the pictures to do the same with graphical tools. There are only a few commands to do everything I told you before.

Start the Terminal. You will find this program by the way ''Applications > Tools > Terminal''. You will see that we must do the same steps as before but you can read them in a text form.

First of all you need to set the root password. If you didn't this before then use the first command line. If you want to change an existing password then use the second one.

Server:~ $ mysqladmin -u root password 'secret'
Server:~ $ mysqladmin -u root -p password 'topsecret'

The next steps are creating a new database ''moodle19'' with correct character set and setting up a database user ''moodle'', with an assigned password (IDENTIFIED BY), to administrate the new database ... and if you want, then do the same for ''moodle20''.

Server:~ $ mysqladmin -u root -p create moodle19
Server:~ $ mysql -u root -p

mysql> ALTER DATABASE moodle19 CHARSET 'utf8';
mysql> GRANT ALL PRIVILEGES ON moodle19.* TO moodle@localhost
-> IDENTIFIED BY 'moodle!';
mysql> quit

Server:~ $

That's really all with the Terminal. You are just ready!

==Copy the Moodle files to the web server==

The documents for the web server are saved in the folder ''/Library/WebServer/Documents/''. You will place your Moodle folder here after you got it from http://download.moodle.org. Download the standard package MOODLE_19_WEEKLY because this is the best choice for new servers. Set the owner ''_www'' for the moodle folder ... this is the user for the web server. The folder permissions should be 755 before the installation and 555 after it's done ... please remember to set this later!

You also need the moodledata folder outside of the Documents folder ... so please make one. Go to the folder ''/Library/WebServer/'' and add the folder ''moodledata''. Because I want to install Moodle 1.9.x and Moodle 2.0 dev together on the same Mac server I add two folders ''moodle19'' and ''moodle20'' inside the moodledata folder. Please set the owner ''_www'' for both folders ''moodle19'' and ''moodle20'' and the folder permissions to 755.

cd /Library/WebServer/
mkdir moodledata
mkdir moodledata/moodle19
mkdir moodledata/moodle20
sudo chown -R _www moodledata
sudo chmod -R 755 moodledata

If you'd like to put the moodledata folder on another volume (not a bad idea if you think you'll have a substantial amount of data within the moodle), note that you cannot simply reference it using the /Volumes/<volume_name>/folder syntax during the moodle setup. Instead, you'll need to create the folder (assigning the user and permissions), then create a '''link''' to it within the /Library/WebServer folder. To create the link, use the following command in a terminal window, substituting your data volume and folder name:

cd /Library/WebServer
ln -s /Volumes/Data_Volume/moodledata moodledata

==Run the Moodle installation==
The installation on the Mac server is the same like the installation on every other server.
Open a web browser to http://your-server-address/moodle/install.php to begin the installation process.
On the screen picture and in the shown config.php you see the web address ''your-server-address'' ... it's only a placeholder for a real address or url ... please set yours. Also a user 'moodle' with a password 'moodle' would be very unsafe settings for your installation.

[[Image:moodle-install1.png]]

[[Image:moodle-install2.png]]

The installer generates the config.php automatically and saves it in the folder ''/Library/WebServer/Documents/moodle19''. Please edit the config.php with a text editor and add the line ''date_default_timezone_set('UTC');''. You may change ''UTC'' to your own timezone ... this is needed for PHP 5.3.0. In case you don't know all the relevant time zone identifiers by heart, there is a [http://phpbuilder.com/manual/en/timezones.php list available online].

<?php /// Moodle Configuration File

unset($CFG);

$CFG->dbtype = 'mysql';
$CFG->dbhost = 'localhost';
$CFG->dbname = 'moodle19';
$CFG->dbuser = 'moodle';
$CFG->dbpass = 'moodle';
$CFG->dbpersist = false;
$CFG->prefix = 'mdl_';

$CFG->wwwroot = 'http://your-server-address/moodle19';
$CFG->dirroot = '/Library/WebServer/Documents/moodle19';
$CFG->dataroot = '/Library/WebServer/moodledata/moodle19';
$CFG->admin = 'admin';

$CFG->directorypermissions = 00777; // try 02777 on a server in Safe Mode

date_default_timezone_set('Europe/Berlin'); // timezone for PHP 5.3.0
require_once("$CFG->dirroot/lib/setup.php");
// MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,
// RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.
?>

When the installation is ready you should change the folder permission for ''/Library/WebServer/Documents/moodle19'' to 555 so the web server is not able to write into this folder again.

==Download the language packages==

==Moodle is running ...==
[[Image:moodle-on-macosx-server.png]]

==How to setup the cron job with launchd==

It's really important to start the cron job every 5 minutes. The cron job assists most of Moodle's modules to perform tasks on a scheduled basis. For example, the discussion forums can only mail out copies of new posts to all subscribers if the cron job tells Moodle to do this.

In Mac OS X 10.5 you will find the system daemon ''launchd'' for this service. This daemon offers a standardized interface to any user and all programs started automatically by the system. Please look at http://developer.apple.com/macosx/launchd.html for more information about the configurations and all parameters.

In our case the service should get the web page http://your-server-address/moodle19/admin/cron.php every 5 minutes. The configuration will be done by the file named ''moodle4mac.cron.plist'' which must be placed in the system folder ''/Library/LaunchDaemons/'' ... surely you can use any other file name but it should say something about the function of the service. The extension must be ''.plist''. After any reboot of your Mac server the cron service will start automaticly because the file is placed in the correct system folder.

===Use the graphical way===
You can use Lingon to add a new daemon plist or to edit one. It produces the same text as you can write in your text editor. http://sourceforge.net/projects/lingon/files/

[[Image:macosx-lingon.png]]

===Use a text editor===
Please use a text editor to write the needed file. You can open the Terminal and use the system editors vi or pico. But you can also write the text file with any GUI text editor ... I mostly use TextWrangler ... but do NOT take an editor for formatted texts like Microsoft Word or OpenOffice Writer. You must get pure text!

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>KeepAlive</key><false/>
<key>Label</key><string>moodle4mac.cron</string>
<key>ProgramArguments</key>
<array>
<string>curl</string>
<string>-s</string>
<string>http://your-server-address/moodle19/admin/cron.php</string>
</array>
<key>RunAtLoad</key><true />
<key>StartInterval</key><integer>300</integer>
<key>StandardErrorPath</key><string>/dev/null</string>
<key>StandardOutPath</key><string>/dev/null</string>
</dict>
</plist>

The label string must be the same as the file name is but without the extension ''.plist''. Save the text file ''/Library/LaunchDaemons/moodle4mac.cron.plist''. The owner of the file must be set to the system user ''root''. That's all, really!

===How to start and stop the cron service===
You can start the new cron service in the Terminal.

sudo launchctl load /Library/LaunchDaemons/moodle4mac.cron.plist

The following command would stop the service. If you want to activate changes in the cron service you need to ''unload'' and then to ''load'' the daemon again.

sudo launchctl unload /Library/LaunchDaemons/moodle4mac.cron.plist

===Only one service for two servers?===
For my server I needed to have a cron service for to instances ''moodle19'' and ''moodle20'' ... no problem ... with the typo ''moodle[19-20]'' the server will get a cron service for both instances.

<nowiki>curl -s http://your-server-address/moodle[19-20]/admin/cron.php</nowiki>

To see if the cron service works correctly you should look at the ''access.log'' of your web server. The cron.php should be accessed every 5 minutes ... on my server for both Moodle instances ''moodle19'' and ''moodle20'' ... oh yes, it works!!

192.168.0.220 - - [30/Jul/2009:22:10:56 +0200] "GET /moodle19/admin/cron.php HTTP/1.1" 200 1136
192.168.0.220 - - [30/Jul/2009:22:10:57 +0200] "GET /moodle20/admin/cron.php HTTP/1.1" 200 1403
192.168.0.220 - - [30/Jul/2009:22:11:18 +0200] "OPTIONS * HTTP/1.0" 200 -
192.168.0.220 - - [30/Jul/2009:22:15:56 +0200] "GET /moodle19/admin/cron.php HTTP/1.1" 200 735
192.168.0.220 - - [30/Jul/2009:22:15:57 +0200] "GET /moodle20/admin/cron.php HTTP/1.1" 200 964
192.168.0.220 - - [30/Jul/2009:22:20:56 +0200] "GET /moodle19/admin/cron.php HTTP/1.1" 200 1136
192.168.0.220 - - [30/Jul/2009:22:20:57 +0200] "GET /moodle20/admin/cron.php HTTP/1.1" 200 1365

==How to set up SSL/https in MAMP for a development/test environment==
Following are the steps that I copied from [http://www.webopius.com/content/355/getting-mamp-working-with-ssl-on-os-x webopius web site] (excepted the last steps).
#stop MAMP
#backup your /Applications/MAMP/conf folder
#open a terminal
#enter: ''openssl genrsa -des3 -out server.key 1024''. Enter a password twice.
#enter: ''openssl req -new -key server.key -out server.csr''. Enter the previous password. You need to answer some questions. ''Common name'' expects your local name (for me it was jerome.moodle.local)
#enter: ''openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt''
#enter: ''cp server.key server.tmp''
#enter: ''openssl rsa -in server.tmp -out server.key''. Enter the previous password.
#enter: ''mkdir /Applications/MAMP/conf/ssl''
#enter: cp server.crt /Applications/MAMP/conf/ssl
#enter: cp server.key /Applications/MAMP/conf/ssl
# Edit Applications/MAMP/conf/apache/ssl.conf:
##comment <IfDefine SSL> tag to closing tag (but not the content)
##SSLCertificateFile /Applications/MAMP/conf/ssl/server.crt
##SSLCertificateKeyFile /Applications/MAMP/conf/ssl/server.key
# Edit /Applications/MAMP/conf/apache/httpd.conf:
##Listen 80
##comment <IfDefine SSL> tag to closing tag (but not the content)
# Edit /Application/MAMP/conf/apache/ssl.conf, change the document root (DocumentRoot) for the one you have into /Application/MAMP/conf/apache/httpd.conf
#in a terminal enter: ''cd /Applications/MAMP/bin/apache2/bin''
#enter: ''sudo ./apachectl startssl''
#start MAMP

From now MAMP should start/stop with the SSL support activated. Note that these steps have only be tested with Apache port set to 80 into MAMP preferences.

==How to update with CVS==

==User administration via LDAP==

The following settings will work on 10.5 Server running LDAP - edit them to customize to your own environment. Please note that moodle requires some fields - it is best to have these fields completed in Workgroup Manager on 10.5 Server - otherwise they'll be prompted to enter info into their moodle profile on first login, but the way we've got it set up, moodle can't modify LDAP for security and data integrity. The necessary fields are user name, first name, surname, Email address, City/Town, country, description, ID number.

LDAP SERVER SETTINGS
Host URL = ourserver.example.com
Version = 3
LDAP encoding = utf-8

BIND SETTINGS
Hide passwords = Yes
Distinguished Name = (blank)
Password = (blank)

USER LOOKUP SETTINGS
User type = posixAccount (rfc2307)
Contexts = cn=users,dc=ourserver,dc=example,dc=com
Search subcontexts = Yes
Dereference aliases = No
User attribute = (blank)
Member attribute = (blank)
Member attribute uses dn = (blank)
Object class = (blank)

FORCE CHANGE PASSWORD
Force change password = No
Use standard Change Password Page = No
Password format = Plain text
Password change URL = (blank)

LDAP PASSWORD EXPIRATION SETTINGS
Expiration = no
Expiration warning = 10
Expiration attribute = ""
Grace logins = No
Grace login attribute = (blank)

ENABLE USER CREATION
Create users externally = No
Context for new users = (blank)

COURSE CREATOR
Creators = (blank)

CRON SYNCHRONIZATION SCRIPT
Removed ext user = Keep internal

NTLM SSO
Enable = No
Subnet = (blank)
First name = givenName (On every login, Never, Locked)
Surname = sn (On every login, Never, Locked)
Email address = mail (On every login, Never, Locked)
Phone 1 = (blank)
Phone 2 = (blank)
Department = (blank)
Address = (blank)
City/Town = l (On every login, Never, Locked)
Country = c (On every login, Never, Locked)
Description = description (On every login, Never, Locked)
ID number = uidNumber (On every login, Never, Locked)
Language = (blank)

==See also==
* [[Complete Install Packages for Mac OS X | Complete install packages for Mac OS X 10.4/10.5]]
* [[Step-by-step Guide for Installing Moodle on Mac OS X 10.4 Client|Step by step installation on a Mac OS X 10.4 Client]]
* [[Cron | Installation of cron for Moodle]]
* [[CVS for Administrators]]

* [http://moodle.org/mod/forum/discuss.php?d=24632 Using Moodle: Dynamic DNS Home Server]

[[Category:Administrator]]
[[Category:Installation]]
[[Category:Mac OS X]]

Step by Step Installation on a Mac OS X 10.5 Server

2010-06-17T17:14:13Z

Matthewm1970:

==Overview==
This guide shows all steps for the installation of Moodle on a [http://www.apple.com/server/macosx Mac OS X 10.5 Server]. This server is a commercial product.

This installation guide can't be useful for an installation on MAMP or XAMPP. If you are looking for an easy way to install Moodle on your local machine please use [[Complete Install Packages for Mac OS X | Complete install packages for Mac OS X 10.4/10.5]] that can be downloaded from http://download.moodle.org/macosx/ ... but if you are planning to set up a Moodle internet server on a Mac then you should think about some more security as the ever local package could give.

Please feel free to add your ideas and wishes to the discussion page for this article. You may also write a complete chapter if you tried the facts yourself on your own Mac Server. I am most interested in the "user administration via LDAP" and I hope to get enough ideas how to get all Mac users into the Moodle user list automaticly.

==System requirements==

+ Apple Computer
+ Mac mini, Mac Pro or Xserve
+ Processor: Intel Core 2 Duo
+ RAM: 2 GB or better
+ Hard Disk: 500 MB free
+ System Software: Mac OS X 10.5 Server

==Install PHP 5.3.0 and the GD Library on the Mac OS X 10.5 Server==

<div style="background-color: yellow; padding: 5px;">Note: If you want to install Moodle 1.8.x on the server you need to get the Entropy PHP-5.2.9-7.pkg for the following steps. Moodle 1.8.9 does not run with PHP 5.3.0 in this moment. All the other things should work in the same way for all Moodle versions.</div>

The Mac OS X Server 10.5.6 Leopard comes with PHP 5.2.6 ... this is correct for Moodle 1.9.x. But you have to add the missing GD Library support to get Moodle running on your server. For Moodle 2.0 the server needs PHP 5.2.8 (or better) and some more PHP extensions ... in this case you must get a better PHP version. These instructions are helpful in both cases.

To see which PHP version and extensions are installed on your server you should edit the file ''/Library/WebServer/Documents/info.php''. You must activate the function call phpinfo() by deleting the both slashes // at the start of the function line. After saving the file you can get all PHP informations in your browser. Please look at http://your-server-address/info.php ... you will not find any GD library support ... bad thing for Moodle!!

<?php
// You can use Server Admin to enable the Apache PHP module; it's disabled by default.
// You can uncomment the phpinfo() directive below to provide a default PHP info page
// but note that this displays information about your host's configuration.
phpinfo();
?>

The easiest way to get the GD library support and to get a better PHP version would be the installation of the complete PHP 5.3.0 package from http://www.entropy.ch/software/macosx/php/. Marc Liyanage precompiled this package to use it on Mac clients and Mac servers. Please get the package and install it by following the instructions on the download page. The installer does everything for you ... it copies PHP into the correct folder ''/usr/local/php5'' and changes its owner to ''root'' automatically.

Now the Apache web server must get knowledge that you want to use the new PHP library instead of the old. Open the application Server Admin to switch to the new library. Go to the web server settings and find the entry php5_module. The normal place for PHP the Mac server is ''libexec/apache2/libphp5.so''. Please change to ''/usr/local/php5/libphp5.so'' and save the settings.

[[Image:Server-admin.png]]

The second thing to configure is the file php.ini. You will find this file inside the new package folder. Open the file ''/usr/local/php5/lib/php.ini'' and edit some settings for Moodle. Most of the settings are okay but not all of them. To communicate to the MySQL database with PHP you have to set the default socket name for local MySQL connects. The default socket name for local MySQLi connects is needed for Moodle 2.0.

If you want to upload any file to your Moodle you should add a little bit more upload size in php.ini. If your server can't use more than 1 GB RAM you should set the memory_limit to a value less than 128M ... but it should have more than 48M for Moodle 1.9 and Moodle 2.0. Note that these sections are not likely to be consecutive in the php.ini file; the quickest way to find each one is search on the initial term (such as 'mysql.default_socket').

; Default socket name for local MySQL connects.
; If empty, uses the built-in MySQL defaults.
mysql.default_socket = /var/mysql/mysql.sock

; Default socket name for local MySQL connects.
; If empty, uses the built-in MySQL defaults.
mysqli.default_socket = /var/mysql/mysql.sock

; Maximum amount of memory a script may consume (128MB)
memory_limit = 128M

; Maximum allowed size for uploaded files.
upload_max_filesize = 128M

; Maximum size of POST data that PHP will accept.
post_max_size = 128M

That's all ... save the file php.ini and restart the web server. Now you should look at http://your-server-address/info.php again. I hope that everything will be okay. You will find the version number PHP 5.3.0 and the running GD library support. Congratulations ... the first step for Moodle on the Mac server is done!

[[Image:phpinfo.png]]

[[Image:phpinfo2.png]]

==Configure the MySQL database for your Moodle installation==

In standard case the database MySQL is installed on the Mac OS X 10.5 Server but it is not running yet. Please make sure that you start the MySQL database server.

===Use the graphical way===
Sorry ... there are some more installations and a lot of clicks to configure MySQL in a graphical way.

First of all start the ''Server Admin''. You will find this program by the way ''Applications > Server > Server Admin''. Activate MySQL on the local server. You must set the password for the user ''root'' before you can start MySQL.

For the next you must download the MySQL database administration tool '''phpMyAdmin''' from http://www.phpmyadmin.net . Move the folder to the web server documents as ''/Library/WebServer/Documents/phpMyAdmin''.

Add the security phrase to the file ''config.inc.php'' in between the single quotes on the line $cfg['blowfish_secret'] = ''; /* YOU MUST FILL IN THIS FOR COOKIE AUTH! */

Now you will be able to start http://your-server-address/phpMyAdmin/ in your browser and to log into the database as the user ''root''. Add a database ''moodle19''. Add a database user ''moodle'' to the server ''localhost''. Don't forget to set a secure password. The database user ''moodle'' should be allowed to administrate the database ''moodle19'' only. It is a bad way to set ''root'' to administrate the database ''moodle19''. If you want to install also Moodle 2.0 dev please add a second database ''moodle20'' and use the same database user for it.

phpMyAdmin is a nice thing to look into the database while Moodle is running for some time. It's much easier to see in the graphical interface than in the command line tools. The image shows the database after Moodle 1.9 and Moodle 2.0 were already installed on this server.

[[Image:phpmyadmin.png]]

===Use the Terminal===
If you want a quick installation then don't fear to use the Terminal. It's easier to tell you all the commands for the right way with the Terminal than showing you all the pictures to do the same with graphical tools. There are only a few commands to do everything I told you before.

Start the Terminal. You will find this program by the way ''Applications > Tools > Terminal''. You will see that we must do the same steps as before but you can read them in a text form.

First of all you need to set the root password. If you didn't this before then use the first command line. If you want to change an existing password then use the second one.

Server:~ $ mysqladmin -u root password 'secret'
Server:~ $ mysqladmin -u root -p password 'topsecret'

The next steps are creating a new database ''moodle19'' with correct character set and setting up a database user ''moodle'', with an assigned password (IDENTIFIED BY), to administrate the new database ... and if you want, then do the same for ''moodle20''.

Server:~ $ mysqladmin -u root -p create moodle19
Server:~ $ mysql -u root -p

mysql> ALTER DATABASE moodle19 CHARSET 'utf8';
mysql> GRANT ALL PRIVILEGES ON moodle19.* TO moodle@localhost
-> IDENTIFIED BY 'moodle!';
mysql> quit

Server:~ $

That's really all with the Terminal. You are just ready!

==Copy the Moodle files to the web server==

The documents for the web server are saved in the folder ''/Library/WebServer/Documents/''. You will place your Moodle folder here after you got it from http://download.moodle.org. Download the standard package MOODLE_19_WEEKLY because this is the best choice for new servers. Set the owner ''_www'' for the moodle folder ... this is the user for the web server. The folder permissions should be 755 before the installation and 555 after it's done ... please remember to set this later!

You also need the moodledata folder outside of the Documents folder ... so please make one. Go to the folder ''/Library/WebServer/'' and add the folder ''moodledata''. Because I want to install Moodle 1.9.x and Moodle 2.0 dev together on the same Mac server I add two folders ''moodle19'' and ''moodle20'' inside the moodledata folder. Please set the owner ''_www'' for both folders ''moodle19'' and ''moodle20'' and the folder permissions to 755.

cd /Library/WebServer/
mkdir moodledata
mkdir moodledata/moodle19
mkdir moodledata/moodle20
sudo chown -R _www moodledata
sudo chmod -R 755 moodledata

If you'd like to put the moodledata folder on another volume (not a bad idea if you think you'll have a substantial amount of data within the moodle), note that you cannot simply reference it using the /Volumes/<volume_name>/folder syntax during the moodle setup. Instead, you'll need to create the folder (assigning the user and permissions), then create a '''link''' to it within the /Library/WebServer folder. To create the link, use the following command in a terminal window, substituting your data volume and folder name:

cd /Library/WebServer
ln -s /Volumes/Data_Volume/moodledata moodledata

==Run the Moodle installation==
The installation on the Mac server is the same like the installation on every other server.
Open a web browser to http://your-server-address/moodle/install.php to begin the installation process.
On the screen picture and in the shown config.php you see the web address ''your-server-address'' ... it's only a placeholder for a real address or url ... please set yours. Also a user 'moodle' with a password 'moodle' would be very unsafe settings for your installation.

[[Image:moodle-install1.png]]

[[Image:moodle-install2.png]]

The installer generates the config.php automatically and saves it in the folder ''/Library/WebServer/Documents/moodle19''. Please edit the config.php with a text editor and add the line ''date_default_timezone_set('UTC');''. You may change ''UTC'' to your own timezone ... this is needed for PHP 5.3.0.

<?php /// Moodle Configuration File

unset($CFG);

$CFG->dbtype = 'mysql';
$CFG->dbhost = 'localhost';
$CFG->dbname = 'moodle19';
$CFG->dbuser = 'moodle';
$CFG->dbpass = 'moodle';
$CFG->dbpersist = false;
$CFG->prefix = 'mdl_';

$CFG->wwwroot = 'http://your-server-address/moodle19';
$CFG->dirroot = '/Library/WebServer/Documents/moodle19';
$CFG->dataroot = '/Library/WebServer/moodledata/moodle19';
$CFG->admin = 'admin';

$CFG->directorypermissions = 00777; // try 02777 on a server in Safe Mode

date_default_timezone_set('Europe/Berlin'); // timezone for PHP 5.3.0
require_once("$CFG->dirroot/lib/setup.php");
// MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,
// RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.
?>

When the installation is ready you should change the folder permission for ''/Library/WebServer/Documents/moodle19'' to 555 so the web server is not able to write into this folder again.

==Download the language packages==

==Moodle is running ...==
[[Image:moodle-on-macosx-server.png]]

==How to setup the cron job with launchd==

It's really important to start the cron job every 5 minutes. The cron job assists most of Moodle's modules to perform tasks on a scheduled basis. For example, the discussion forums can only mail out copies of new posts to all subscribers if the cron job tells Moodle to do this.

In Mac OS X 10.5 you will find the system daemon ''launchd'' for this service. This daemon offers a standardized interface to any user and all programs started automatically by the system. Please look at http://developer.apple.com/macosx/launchd.html for more information about the configurations and all parameters.

In our case the service should get the web page http://your-server-address/moodle19/admin/cron.php every 5 minutes. The configuration will be done by the file named ''moodle4mac.cron.plist'' which must be placed in the system folder ''/Library/LaunchDaemons/'' ... surely you can use any other file name but it should say something about the function of the service. The extension must be ''.plist''. After any reboot of your Mac server the cron service will start automaticly because the file is placed in the correct system folder.

===Use the graphical way===
You can use Lingon to add a new daemon plist or to edit one. It produces the same text as you can write in your text editor. http://sourceforge.net/projects/lingon/files/

[[Image:macosx-lingon.png]]

===Use a text editor===
Please use a text editor to write the needed file. You can open the Terminal and use the system editors vi or pico. But you can also write the text file with any GUI text editor ... I mostly use TextWrangler ... but do NOT take an editor for formatted texts like Microsoft Word or OpenOffice Writer. You must get pure text!

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>KeepAlive</key><false/>
<key>Label</key><string>moodle4mac.cron</string>
<key>ProgramArguments</key>
<array>
<string>curl</string>
<string>-s</string>
<string>http://your-server-address/moodle19/admin/cron.php</string>
</array>
<key>RunAtLoad</key><true />
<key>StartInterval</key><integer>300</integer>
<key>StandardErrorPath</key><string>/dev/null</string>
<key>StandardOutPath</key><string>/dev/null</string>
</dict>
</plist>

The label string must be the same as the file name is but without the extension ''.plist''. Save the text file ''/Library/LaunchDaemons/moodle4mac.cron.plist''. The owner of the file must be set to the system user ''root''. That's all, really!

===How to start and stop the cron service===
You can start the new cron service in the Terminal.

sudo launchctl load /Library/LaunchDaemons/moodle4mac.cron.plist

The following command would stop the service. If you want to activate changes in the cron service you need to ''unload'' and then to ''load'' the daemon again.

sudo launchctl unload /Library/LaunchDaemons/moodle4mac.cron.plist

===Only one service for two servers?===
For my server I needed to have a cron service for to instances ''moodle19'' and ''moodle20'' ... no problem ... with the typo ''moodle[19-20]'' the server will get a cron service for both instances.

<nowiki>curl -s http://your-server-address/moodle[19-20]/admin/cron.php</nowiki>

To see if the cron service works correctly you should look at the ''access.log'' of your web server. The cron.php should be accessed every 5 minutes ... on my server for both Moodle instances ''moodle19'' and ''moodle20'' ... oh yes, it works!!

192.168.0.220 - - [30/Jul/2009:22:10:56 +0200] "GET /moodle19/admin/cron.php HTTP/1.1" 200 1136
192.168.0.220 - - [30/Jul/2009:22:10:57 +0200] "GET /moodle20/admin/cron.php HTTP/1.1" 200 1403
192.168.0.220 - - [30/Jul/2009:22:11:18 +0200] "OPTIONS * HTTP/1.0" 200 -
192.168.0.220 - - [30/Jul/2009:22:15:56 +0200] "GET /moodle19/admin/cron.php HTTP/1.1" 200 735
192.168.0.220 - - [30/Jul/2009:22:15:57 +0200] "GET /moodle20/admin/cron.php HTTP/1.1" 200 964
192.168.0.220 - - [30/Jul/2009:22:20:56 +0200] "GET /moodle19/admin/cron.php HTTP/1.1" 200 1136
192.168.0.220 - - [30/Jul/2009:22:20:57 +0200] "GET /moodle20/admin/cron.php HTTP/1.1" 200 1365

==How to set up SSL/https in MAMP for a development/test environment==
Following are the steps that I copied from [http://www.webopius.com/content/355/getting-mamp-working-with-ssl-on-os-x webopius web site] (excepted the last steps).
#stop MAMP
#backup your /Applications/MAMP/conf folder
#open a terminal
#enter: ''openssl genrsa -des3 -out server.key 1024''. Enter a password twice.
#enter: ''openssl req -new -key server.key -out server.csr''. Enter the previous password. You need to answer some questions. ''Common name'' expects your local name (for me it was jerome.moodle.local)
#enter: ''openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt''
#enter: ''cp server.key server.tmp''
#enter: ''openssl rsa -in server.tmp -out server.key''. Enter the previous password.
#enter: ''mkdir /Applications/MAMP/conf/ssl''
#enter: cp server.crt /Applications/MAMP/conf/ssl
#enter: cp server.key /Applications/MAMP/conf/ssl
# Edit Applications/MAMP/conf/apache/ssl.conf:
##comment <IfDefine SSL> tag to closing tag (but not the content)
##SSLCertificateFile /Applications/MAMP/conf/ssl/server.crt
##SSLCertificateKeyFile /Applications/MAMP/conf/ssl/server.key
# Edit /Applications/MAMP/conf/apache/httpd.conf:
##Listen 80
##comment <IfDefine SSL> tag to closing tag (but not the content)
# Edit /Application/MAMP/conf/apache/ssl.conf, change the document root (DocumentRoot) for the one you have into /Application/MAMP/conf/apache/httpd.conf
#in a terminal enter: ''cd /Applications/MAMP/bin/apache2/bin''
#enter: ''sudo ./apachectl startssl''
#start MAMP

From now MAMP should start/stop with the SSL support activated. Note that these steps have only be tested with Apache port set to 80 into MAMP preferences.

==How to update with CVS==

==User administration via LDAP==

The following settings will work on 10.5 Server running LDAP - edit them to customize to your own environment. Please note that moodle requires some fields - it is best to have these fields completed in Workgroup Manager on 10.5 Server - otherwise they'll be prompted to enter info into their moodle profile on first login, but the way we've got it set up, moodle can't modify LDAP for security and data integrity. The necessary fields are user name, first name, surname, Email address, City/Town, country, description, ID number.

LDAP SERVER SETTINGS
Host URL = ourserver.example.com
Version = 3
LDAP encoding = utf-8

BIND SETTINGS
Hide passwords = Yes
Distinguished Name = (blank)
Password = (blank)

USER LOOKUP SETTINGS
User type = posixAccount (rfc2307)
Contexts = cn=users,dc=ourserver,dc=example,dc=com
Search subcontexts = Yes
Dereference aliases = No
User attribute = (blank)
Member attribute = (blank)
Member attribute uses dn = (blank)
Object class = (blank)

FORCE CHANGE PASSWORD
Force change password = No
Use standard Change Password Page = No
Password format = Plain text
Password change URL = (blank)

LDAP PASSWORD EXPIRATION SETTINGS
Expiration = no
Expiration warning = 10
Expiration attribute = ""
Grace logins = No
Grace login attribute = (blank)

ENABLE USER CREATION
Create users externally = No
Context for new users = (blank)

COURSE CREATOR
Creators = (blank)

CRON SYNCHRONIZATION SCRIPT
Removed ext user = Keep internal

NTLM SSO
Enable = No
Subnet = (blank)
First name = givenName (On every login, Never, Locked)
Surname = sn (On every login, Never, Locked)
Email address = mail (On every login, Never, Locked)
Phone 1 = (blank)
Phone 2 = (blank)
Department = (blank)
Address = (blank)
City/Town = l (On every login, Never, Locked)
Country = c (On every login, Never, Locked)
Description = description (On every login, Never, Locked)
ID number = uidNumber (On every login, Never, Locked)
Language = (blank)

==See also==
* [[Complete Install Packages for Mac OS X | Complete install packages for Mac OS X 10.4/10.5]]
* [[Step-by-step Guide for Installing Moodle on Mac OS X 10.4 Client|Step by step installation on a Mac OS X 10.4 Client]]
* [[Cron | Installation of cron for Moodle]]
* [[CVS for Administrators]]

* [http://moodle.org/mod/forum/discuss.php?d=24632 Using Moodle: Dynamic DNS Home Server]

[[Category:Administrator]]
[[Category:Installation]]
[[Category:Mac OS X]]