expoweb/handbook/troggle/otherscripts.html

51 lines
3.5 KiB
HTML

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Other scripts supporting troggle</title>
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expedition Handbook</h2>
<h1>Other scripts</h1>
<p>Apart from these scripts, troggle in full deployment also needs a running mySQL database, a running apache webserver and cgit to display git repos.
<h3 id="inscripts">Scripts</a></h3>
<ul>
<li><a href="">make-folklist.py</a> turns the folk.csv file into a webpage.
<li><a href="">updatephotos</a> generates navigable webpages from annual directories of photo images
<li><a href="">wallets.py</a> generates statuspages and to-do list pages for survey data production.
<li><a href="">make_essentials.sh</a> generates GPS tracks and routes for surface walking
<li><a href="">make_svx.sh</a> generates surface Survex tracks
<li><a href="">svxtrace.py</a> analyses Survex tracks to help find errors
<li><a href="">chk-refs.sh</a> analyses Survex files and wallets files to find reference errors
<li><a href="">create_dplong_table.py</a> Creates and updates the lengths and depths of all the caves
<li><a href="">make-areaindices.py</a> (obsolete?)
<li><a href="">make-prospectingguide-new.py</a> and <a href="">prospecting_guide_short.py</a> - unmaintained
<li><a href="">boe</a> Bank of Expo runs the accounts preceding and during expo
<li><a href="">bierbook.tex</a> LaTeX script for generating the bierbook - a new list of names and dates each year
<li><a href="">seshbook.tex</a> LaTeX script for generating the seshbook - works from the same list of names
<li><a href="">therionpage.tex</a> LaTeX script anbd makefile for generating therion-style protractors
</ul>
<p>There are also scripts running cron jobs on the server to fix file permissions and to periodically tidy repositories, and example rsync and scp scripts to help manage synchronisation of the expofiles directories which are not under version control.
<h4 id="wallets">Wallets</a></h4>
<p><a href="../survey/onlinewallet.html">Online wallets</a> are maintained using the <a href="">wallets.py</a> script, but troggle also directly imports all the expofiles/surveyscans/ directories of scanned survey notes.
<h4 id="survex">Survex files</a></h4>
<p>Survex files contain a reference to the wallet which contains the original survey notes for that surveyed passage. These sometimes have errors and also get out of date as caves get renamed when they get a kataster number issued. Each online survey wallet also has a reference to the survex file(s) which have been typed up from that data.
<h4 id="folk">Folk</a></h4>
<p><a href="../computing/folkupdate.html">Folk update</a> process produces a webpage listing all expo participants but it also runs some validation checks on the input file /folk/folk.csv . Troggle also directly imports folk.csv so that it knows who everyone is, but errors during the importing are not as easy to see as validation errors printed when running the <a href="">make-folklist.py</a> script.
<h4 id="photos">Photos</a></h4>
<p><a href="">updatephotos</a> uses the BINS package to generate the webpages. BINS is no longer maintained by its author so expo has taken on the responsibility for keeping it running. (Wookey is in the process of packaging it as a proper debian package).
<hr />
Go on to: <a href="trogarch.html">Troggle architecture</a><br />
Return to: <a href="trogintro.html">Troggle intro</a><br />
<hr />
</body>
</html>