aslo .xo updater proposal
April 21, 2009 – 11:24 pmProposal 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:
- 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.)
- 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.)
- Have the server hosting aslo run a sql query to add the new .xo file to the relevant database.
- Somehow work out any concurrency issues that might occur.
Thoughts? Takers?
One Response to “aslo .xo updater proposal”
> 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.)
You can instead do this as a post-update hook in GIT, which has advantages of not polling, and already knowing that there’s been an update.
Other than that, all sounds good; we didn’t do this previously because we thought activity maintainers should decide when they were ready to make releases, but the suggestion of a “stable” branch that you only push when you want to release eliminates that concern, at the cost of maintainers having to juggle git branches if they want to use the feature. So, rock on, I say.
By Chris on Apr 22, 2009