3
3
* Mahara: Electronic portfolio, weblog, resume builder and social networking
4
* Copyright (C) 2006-2008 Catalyst IT Ltd (http://www.catalyst.net.nz)
4
* Copyright (C) 2006-2009 Catalyst IT Ltd and others; see:
5
* http://wiki.mahara.org/Contributors
6
7
* This program is free software: you can redistribute it and/or modify
7
8
* it under the terms of the GNU General Public License as published by
21
22
* @author Catalyst IT Ltd
22
23
* @license http://www.gnu.org/copyleft/gpl.html GNU GPL
23
* @copyright (C) 2006-2008 Catalyst IT Ltd http://catalyst.net.nz
24
* @copyright (C) 2006-2009 Catalyst IT Ltd http://catalyst.net.nz
58
59
// system mail address. emails out come from this address.
59
60
// if not specified, will default to noreply@ automatically detected host.
60
61
// if that doesn't work or you want something else, then specify it here.
61
// $cfg->noreplyaddress = 'noreply@myhost.com'
62
// $cfg->noreplyaddress = 'noreply@myhost.com';
63
64
// Logging configuration
64
65
// For each log level, you can specify where the messages are displayed.
65
67
// LOG_TARGET_SCREEN makes the error messages go to the screen - useful
66
68
// when debugging but not on a live site!
69
// LOG_TARGET_ADMIN sends error messages to the screen but only when
70
// browsing in the admin section
67
71
// LOG_TARGET_ERRORLOG makes the error messages go to the log as specified
68
72
// by the apache ErrorLog directive. It's probably useful to have this on
69
73
// for all log levels.
70
// You can combine them with bitwise operations,
74
// LOG_TARGET_FILE allows you to specify a file that messages will be logged
75
// to. It's best to pick a path in dataroot, but note that logfiles tend to get
76
// very large over time - so it's advisable to implement some kind of logrotate
77
// if you want to leave this on all the time. The other option is to just turn
78
// this on when you are getting some kind of error or want to see the logging,
79
// and know that you're not going to let the logfile get large.
81
// You can combine the targets with bitwise operations,
71
82
// e.g. LOG_TARGET_SCREEN | LOG_TARGET_ERRORLOG
73
84
// This configuration is suitable for people running Mahara for the first
87
98
//$cfg->log_warn_targets = LOG_TARGET_SCREEN | LOG_TARGET_ERRORLOG;
88
99
//$cfg->log_environ_targets = LOG_TARGET_SCREEN | LOG_TARGET_ERRORLOG;
101
// If you use LOG_TARGET_FILE, this is the file that errors will be logged to.
102
// It's best to pick a path under dataroot, as we know we can write there.
103
$cfg->log_file = $CFG->dataroot . '/error.log';
90
105
// The log levels that will generate backtraces. Useful for development,
91
106
// but probably only warnings are useful on a live site.
92
107
$cfg->log_backtrace_levels = LOG_LEVEL_WARN | LOG_LEVEL_ENVIRON;
104
119
// These options are a performance hit otherwise, enable when you are
105
120
// developing for Mahara
106
121
$cfg->developermode = false;
122
// $cfg->developermode = DEVMODE_DEBUGJS | DEVMODE_DEBUGCSS | DEVMODE_FIREBUGLITE | DEVMODE_UNPACKEDJS;
108
124
// Whether to send e-mail. If set to false, Mahara will not send any e-mail at
109
125
// all. This is useful for when setting up development versions of Mahara where
138
154
// paths and arguments for various system commands
139
155
$cfg->pathtounzip = '/usr/bin/unzip';
156
$cfg->pathtozip = '/usr/bin/zip';
157
$cfg->ziprecursearg = '-r';
140
158
$cfg->unzipdirarg = '-d';
141
159
// some shared hosts have restrictions on where unzip can be used
142
160
// dataroot is often not allowed; but /tmp is
158
176
// Whether to show the onlineusers sideblock
159
177
$cfg->showonlineuserssideblock = true;
179
// CRON job maximum run age in SECONDS
180
// ... Mahara decides to run a cron job only if the "next run time" is between the current date+time and (max run age) seconds ago.
182
// IMPORTANT: THIS MUST BE EQUAL TO OR GREATER THAN YOUR CRON JOB THAT HITS {$cfg->wwwroot}/lib/cron.php
183
// ... The setup/install instructions require you to set a server cron job to hit the cron.php.
184
// ... The default assumption by Mahara is that this will be every minute.
185
// ... Not all hosting providers will allow you to schedule a cron job every minute. Also, you may for your own purposes
186
// not want to have a cron job every minute for CPU / performance reasons.
188
// If this is not set properly, any cron periodicities less than your server cron periodicity will likely be perpetually skipped.
189
// This will be evident in cron job report that is output by your server after hitting cron.php.
191
// EXAMPLE: Your cron job hits cron.php every 15 minutes. Then $cfg->maxrunage must be 900 or greater.
192
$cfg->maxrunage = 300;