Proposal from Ben Fisher for aslo:

When an activity's git repository's "stable" branch is updated, the .xo file available for download on aslo should update too. How can this be done? Here's his rough outline:

  1. Have a shell script on a cron job that git updates each activity and (if changes have occured) rebuilds a new .xo file. (This can run on any computer.)
  2. Have that script also copy the new .xo file to the location .xo files are stored on the aslo server, with the proper name. (This requires special access to the server running aslo.)
  3. Have the server hosting aslo run a sql query to add the new .xo file to the relevant database.
  4. Somehow work out any concurrency issues that might occur.

Thoughts? Takers?