open id

checked on adding openid to catalyst, but it seems broken and not used much.

todo

Although it is nice to know about the schema, I think the next step should be working on the checklist server to prepare it for software engineering.  And I think I should keep that as a separate database since it is student accessible.

I want to improve the logging/communication of the 436 and 446 students.  Tomorrow I'll work on the syllabi for those courses and 336 and then look at the evaluation mechanisms and see what I need to implement to make it work well.

I need to start working on the videos for 336 also.

catalyst, postgresql and schemas

the idea here is to use multiple schemas instead of databases to reduce redundancy,

the basic catalyst create model doesn't seem to handle non default schemas, so I created one with the default schema,

oops, I found the option after working through the loader documentation and making my own script.  it is odd because I don't see where the selection shows up in the source files.

much later:
I still have not found where it is identifying the schema used.  I tried some different experiments though and it is distinguishing between the two versions of the same table/view.  My current guess is that since it is inaccessible from one of the roles that it is skipping it.  It would be nice though if it was explicitly stated somewhere.

postgresql config

actually the next step is to migrate the configuration files so I can connect from other places.

ppa forwarding

to upgrade the database, I need to add a ppa archive, but the outbound
port is blocked, the port number is 11371

on db:

on server:
sysctl net.netfilter.nf_conntrack_acct=1
sysctl net.ipv4.ip_forward=1

and then the rules
iptables --append FORWARD -j ACCEPT
iptables -t nat --append POSTROUTING  -j MASQUERADE

and then on the client I set the gw for that host to be server.

The above may be a bit overkill, but it worked.  I tried using iptables on the client to forward the packets without setting the gateway, but I didn't have any luck with that.

Now onto upgrading postgres.

First backup with pg_dumpall

Next aptitude dist-upgrade

Then use psql to reimport the data, and it looks ok.

the next task is to connect to a different schema than public using perl

attendance/usage tracking

I have a separate database for attendance tracking, I think I am going to merge it into the department one though to reduce redundancy.

First though, I'm going to back up the databases, and then try to upgrade them to version 9

ldap admin

worked on web app to help manage the ldap group that contains add-ons to the allowed user list.  It works well and should be useful.