mirror of
https://github.com/cs341-illinois/coursebook.git
synced 2026-10-01 23:54:40 +08:00
Lawrence Angrave
73a0f1e976
The website consumes the wiki through the _coursebook submodule and updates it with --remote, so the SHA recorded in the site's tree never affects what deploys. It had drifted months behind as a result, which is a trap for anyone who runs a plain 'git submodule update' and then builds a stale book. The trigger commit this script already pushes is the natural place to fix that: point the gitlink at the wiki commit push_to_wiki.sh just published, so the recorded pointer matches reality at no extra cost. ls-remote plus update-index writes the gitlink directly, so the shallow clone never has to fetch the submodule. Both steps are non-fatal. The push is what rebuilds the site, and under 'set -e' a transient ls-remote failure would otherwise skip it. The commit keeps --allow-empty so an already-current pointer still triggers a build.
Scripts
__init__.pyInit to make a python packagedeploy.shScript to run in travis deploy stagescript.shScript to run in travis script stagesinstall.shScript to run in travis install stagegen_order.pyGenerates the latex order file from the yaml filegen_wiki.pyGenerates a wiki given an order file and output directorypandoc_header_filter.pyOutputs a yaml block to stderr given the metadata of the filepandoc_wiki_filter.pyFilters a latex wiki page with additional add onspush_to_wiki.shScript to run in the push to wiki stagesite_cleanup.shScript to clean up pushing to the sitesite_deploy.shScript to deploy to the sitesite_retry.shScript to retry