|
|
|
Environment:
|
Any environment that support PHP
|
|
|
Help Moodle run in a heavy environment (either big Moodles or many multiple Moodles).
* Adapt all the DB installation and upgrade scripts to run from the command line, so fully scripted installations are possible without using the web interface.
* Develop a profiling system for developers to use when testing their code. Aim to spot and fix performance bottlenecks in Moodle with good reports and suggestions about what developers could do.
|
|
Description
|
Help Moodle run in a heavy environment (either big Moodles or many multiple Moodles).
* Adapt all the DB installation and upgrade scripts to run from the command line, so fully scripted installations are possible without using the web interface.
* Develop a profiling system for developers to use when testing their code. Aim to spot and fix performance bottlenecks in Moodle with good reports and suggestions about what developers could do. |
Show » |
made changes - 03/Jan/08 07:35 AM
| Field |
Original Value |
New Value |
|
Security
|
Possible security issue
[ 10002
]
|
|
made changes - 11/Jan/09 03:04 AM
|
Assignee
|
Martin Dougiamas
[ dougiamas
]
|
Petr ?koda
[ skodak
]
|
|
Fix Version/s
|
|
2.0
[ 10122
]
|
|
New Feature
Open
Major
Develop feature for Moodle which enable it to run in a heavy environment including commandline installer,upgrader, profiling systems, etc.
For this upgrade script automation, would it include a way to upgrade non-core modules and plugins too? Something along the lines of an automated check for a compatible version e.g. 2.0, followed by downloading and copying the file to the right location before the main upgrade process, a bit like the language pack interface works. Or is this a totally separate issue?