<li><ahref="scriptscurrent.html#prosp">make-prospectingguide-new.py</a> and <ahref="">prospecting_guide_short.py</a><ahref="../../noinfo/make-areaindices.py">make-areaindices.py</a> - (unmaintained?)</li><br/>
<li><ahref="scriptscurrent.html#dplong">create_dplong_table.py</a> Creates and updates the lengths and depths of all the caves.
<li><ahref="scriptscurrent.html#cavestats">cavestats</a> and <ahref="scriptscurrent.html#cavestats">smklengths </a> extract overall lengths and depths from all the survex files
<li><ahref="scriptscurrent.html#summ">summarizecave.sh</a> gets .3d file contents using survex
<li><ahref="scriptscurrent.html#tabular">caves-tabular.html</a> a re-sortable table of cave data
<li><ahref="scriptscurrent.html#js">JavaScript</a> packages are used by some troggle pages. See <ahref="serverconfig.html#js">the Expo server page</a>.
<p>There are also scripts running cron jobs on the server to fix file permissions and to periodically tidy <ahref="../computing/repos.html">repositories</a>, and example rsync and scp scripts to help manage synchronisation of the expofiles directories which are not under version control.
<p>Apart from these scripts, troggle in full deployment also needs <br>- a running mySQL database, <br>- a running apache webserver and <br>- cgit to display git repos.
<p>There were perl and python scripts scattered through the :drawings: and :loser: (svx files) repos. Not all of the functions in these scripts have been recreated in more recent scripts or programmed into troggle.
<h3id="newscript">When you write a script</a></h3>
<p>Any script that generates an HTML file should insert <em><meta name="keywords" content="NOEDIT"></em>
in the HTML header. Then when troggle renders the page it will not allow the user to edit the generated page. See <ahref="../computing/hbmanual1.html">handbook editing</a> for a fuller explanation of troggle post-processing.