okfn/dashboard — Issue #24: Rearchitect server cron jobs
Author: zephod
Created: 2012-01-20 16:47:29+00:00
State: open

At present, Wordpress front end runs a cron task, `~/cronjob_list_members.sh`. This connects to the remote DB server, pulls the members list, and uses regexes to hack it into a CSV file which it places in a public directory.

Problems:
* Piping SQL results through `sed` to create a CSV? Really?
* We've discovered any file made public on the wp server (eg. `http://okfn.org/dashboard/file.csv`) will also appear on all sites in the multisite (eg `http://openglam.net/dashboard/file.csv`), making a mess.

Suggest the cron job runs on the server, using `SELECT INTO OUTFILE` to avoid the `sed` mess, and uploads it somewhere public. For example it could push it to a repo on GitHub.

The Dashboard gather script just needs a public up-to-date CSV file of members.