Custom Query (196 matches)

Apparently restarting slapd (now that we sort of can do so) will break whoisd because it only opens a single connection when it starts up. We should make it try to reconnect if it loses that connection so that the whois webapp doesn't silently break.

Aside from making sure that the replicas themselves are okay and replication is running, we should have Nagios check the replicated suffix to see whether there are any records containing the nsds5ReplConflict attribute, which indicates a conflict that could not be automatically resolved.

Moodle is a highly popular open-source CMS for classes/the educational market. I've heard regular mumblings that MIT's considering a global install for replacing Stellar, although I don't know how likely that is. In the meantime, it has the potential to be highly useful for SIPB's IAP classes, ESP classes, etc. etc.

I tried installing Moodle 1.9.9+ weekly (as of today). Issues I noticed:

• The README indicates it wants a cronjob to run every five minutes. I guess we could do that but there are a couple of issues with programatically adding cronjobs. I wonder if we can instead avoid it, since it goes against the scripts "if nobody's using your site, it costs no resources other than a couple megabytes of disk space" ethos. MediaWiki?, for instance, has a "job queue" for cleanup stuff like this.
• Moodle recommends the GD extension (and can take advantage of mysqli, mbstring, curl, and xmlrpc if present). Adding an empty php.ini file makes the installer blow up, though. It works if I copy /etc/php.ini and add extension=gd.so, although that sucks. Let's fix ticket #2 instead.
• It wants a directory outside the docroot, so we need the usual ~/Scripts thing that the e.g. Django installer does.
• Once you have that directory outside the docroot writable, you don't need the Moodle directory itself writable; it spits a config.php back at you. We could probably even programatically generate that file from Wizard.
• It seems not to actually let you use mysqli; changing it back to mysql works. I didn't actually debug what was wrong.
• Once you get past the "installer", there are still a few steps like "accepting" the GPL and several screenfuls of creating tables that it wants you to do at first login that we should definitely do automatically.
• Creating tables prints "SHOW TABLES" like a hundred times. What is up with that.
• The new password requirement is unnecessarily onerous ("The password must have at least 8 characters, at least 1 digit(s), at least 1 lower case letter(s), at least 1 upper case letter(s), at least 1 non-alphanumeric character(s)") for a webapp. I would be tempted to bypass it for the initial user, which we probably can if we're automating that setup step, or get cert auth working as soon as we can.

Other than those minor points, it seems to work out of the box, so an autoinstaller should be simple.