Notes from Moodlemoot 2013
At U of M, moodle is their 2nd most critical system after email.
The have a similar setup to U of A in that production instance is loadbalanced, and moodle cron is run on a separate server.
Using moodle's integrated backup system to do daily course backups, history of 10 backups
Using a PHP cache is necessary (doubles performance) U of M uses APC (alternate PHP cache)
Using mysql tuner/mysql enterprise monitor to monitor database health
Daily push of enrolments
courses are named with coursecode-section-semester (ie. MAT10101-A-W13)
currently in house SIS, moving to peoplesoft
single moodle instance
using munin for graphing, nagios for alterting, moving to git for version control/updates, using Hudson (now Jenkins) for server mirroring.
Moodle-Stats for monitoring instance (github moodle-scripts)
agile-scrum and jira/confluence for helpdesk
Leaves courses open for 3 years so that students can still audit them
Teachers responsible for importing content into new courses.
No comments:
Post a Comment