expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2024-11-29 05:11:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

More links to historical stuff and troggle docm to do list

Browse Source
This commit is contained in:
Philip Sargent 2019-02-26 18:19:16 +00:00
parent 0545297254
commit 5d576ab170
4 changed files with 22 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
handbook/manual.html
View File

@ -18,7 +18,7 @@ very welcome to muck in. It is slowly getting better organised.</p>
<p>This manual is organized in a how-to sort of style. The categories, <p>This manual is organized in a how-to sort of style. The categories,
rather than referring to specific elements of the data management system, refer to rather than referring to specific elements of the data management system, refer to
processes that a maintainer would want to do.</p> processes that a maintainer would want to do.</p>
<p>Note that to display the survey data you will need a copy of the survex software. <p>Note that to display the survey data you will need a copy of the <a href="getsurvex.html">survex</a> software.
<h3>Contents</h3> <h3>Contents</h3>

4
handbook/nerd.html
View File

@ -21,8 +21,8 @@
<li><a href="rescue.htm">Rescue guide</a></li> <li><a href="rescue.htm">Rescue guide</a></li>
</ul></li> </ul></li>
<li><a href="../index.htm">Back to Expedition Intro page</a></li> <li><a href="../index.htm">Expedition Intro page</a></li>
<li><a href="../../index.htm">Back to CUCC Home page</a></li> <li><a href="../../index.htm">CUCC Home page</a></li>
</ul> </ul>
</body> </body>
</html> </html>

21
handbook/troggle-ish.html
View File

@ -7,14 +7,25 @@
<body> <body>
<h2 id="tophead">CUCC Expedition Handbook</h2> <h2 id="tophead">CUCC Expedition Handbook</h2>
<h1>Troggle - what you may need to know</h1> <h1>Troggle - what you may need to know</h1>
<p>Troggle is the content management system which runs much of the the cave survey data management and also presents the data on the website and manages the Expo Handbook. <p>Troggle runs much of the the cave survey data management, presents the data on the website and manages the Expo Handbook.
<p>You may have arrived here by accident when where you really need to be is <a href="website-history.html">website history</a>. <p>You may have arrived here by accident when where you really need to be is <a href="website-history.html">website history</a>.
<p>This page is mostly an index to other records of what troggle is and what plans have been made - but never implemented - to improve it.
<br><br> <p>This page needs to be restructured and rewritten so that it describes these things:
<ul>
<li>Day to day troggle tasks - usually during expo. i.e. links to the "survey handbook"
<li>Annual tasks: preparing for next year, finishing last year (troggle & scripts)
<li>Architectural documentation of how it all fits together & list of active scripts
<li>How to edit and maintain troggle itself. The code is public on repository <a href="http://expo.survex.com/repositories/">::troggle::</a>
</ul>
<br>
<tt><em>Everything here should be updated or replaced - this page just records a lot of unfinished ideas. <tt><em>Everything here should be updated or replaced - this page just records a lot of unfinished ideas.
Most people will not want to read this at all. This is for speleosoftwarearcheologists only.</em> Most people will not want to read this at all. This is for speleosoftwarearcheologists only.</em>
</tt> </tt>
<p>This page is mostly an index to other records of what troggle is and what plans have been made - but never implemented - to improve it.
<h3 id="troggle">Troggle - what it is</a></h3> <h3 id="troggle">Troggle - what it is</a></h3>
<p> <p>
@ -64,7 +75,7 @@ All Survex | Scans | Tunneldata | 107 | 161 | 204 | 258 | 264 | Expo2016 | Expo2
</ol> </ol>
<h3>stroggle</h3> <h3>stroggle</h3>
<p>At one time Martin Green attempted to reimplement troggle as "stroggle" using <a href="https://www.fullstackpython.com/flask.html">flask</a> at <p>At one time Martin Green attempted to reimplement troggle as "stroggle" using <a href="https://www.fullstackpython.com/flask.html">flask</a> instead of Django at
<a href="https://en.wikipedia.org/wiki/Gitorious">git@gitorious.org:stroggle/stroggle.git</a> (but gitorious has been deleted).</p> <a href="https://en.wikipedia.org/wiki/Gitorious">git@gitorious.org:stroggle/stroggle.git</a> (but gitorious has been deleted).</p>
<p>A copy of this project is archived by Wookey on <a href="http://wookware.org/software/cavearchive/stroggle/">wookware.org/software/cavearchive/stroggle/</a>. <p>A copy of this project is archived by Wookey on <a href="http://wookware.org/software/cavearchive/stroggle/">wookware.org/software/cavearchive/stroggle/</a>.
@ -74,7 +85,7 @@ All Survex | Scans | Tunneldata | 107 | 161 | 204 | 258 | 264 | Expo2016 | Expo2
from <a href="http://caving.soc.srcf.net/wiki/Troggle">caving.soc.srcf.net/wiki/Troggle</a> from <a href="http://caving.soc.srcf.net/wiki/Troggle">caving.soc.srcf.net/wiki/Troggle</a>
<p>Troggle is a system under development for keeping track of all expo data in a logical and accessible way, and displaying it on the web. At the moment, it is under development at <a rel="nofollow" class="external free" href="http://troggle.cavingexpedition.com/">http://troggle.cavingexpedition.com/</a> <p>Troggle is a system under development for keeping track of all expo data in a logical and accessible way, and displaying it on the web. At the moment, it is under development at <a rel="nofollow" class="external free" href="http://troggle.cavingexpedition.com/">http://troggle.cavingexpedition.com/</a>
<tt>But note that this is Aaron's version of troggle, forked from the version of troggle we use. Aaron uses this for the <a href="https://expeditionwriter.com/new-expedition-to-mount-erebus-antarctica/">Erebus expedition.</tt> <tt>But note that this is Aaron's version of troggle, forked from the version of troggle we use. Aaron uses this for the <a href="https://expeditionwriter.com/new-expedition-to-mount-erebus-antarctica/">Erebus expedition</a>.</tt>
</p> </p>
<p>Note that the information there is incomplete and editing is not yet enabled. <p>Note that the information there is incomplete and editing is not yet enabled.
</p> </p>

6
handbook/website-history.html
View File

@ -41,7 +41,7 @@ A <a href="survexhistory96.htm">history of survex</a> article covering the perio
<h3>Initial cave data management</h3> <h3>Initial cave data management</h3>
<p>Along with centrelines and sketches, descriptions of caves were also affected by improvements <p>Along with centrelines and sketches, descriptions of caves were also affected by improvements
in data management. In a crucial breakthrough, Andrew Waddinton introduced the use of the in data management. In a crucial breakthrough, Andrew Waddinton introduced the use of the
nascent markup language HTML to create an interlinked, navigable system of descriptions. Links nascent markup language HTML to create an interlinked, navigable system of descriptions (see <a href="c21bs.html">"Expo Bullshit"</a>). Links
in HTML documents could mimic the branched and often circular structure of the caves themselves. in HTML documents could mimic the branched and often circular structure of the caves themselves.
For example, the reader could now follow a link out of the main passage into a side passage, and For example, the reader could now follow a link out of the main passage into a side passage, and
then be linked back into the main passage description at the point where the side passage then be linked back into the main passage description at the point where the side passage
@ -116,7 +116,7 @@ This reads in all the logbooks and surveys and provides a nice way to access the
It was separate for a while until Martin Green added code to merge the old static pages and It was separate for a while until Martin Green added code to merge the old static pages and
new troggle dynamic pages into the same site. This is now the live system running everything (in 2019). Work on developing Troggle further still continues sporadically (see <a href="troggle-ish.html">Troggle notes</a>).</p> new troggle dynamic pages into the same site. This is now the live system running everything (in 2019). Work on developing Troggle further still continues sporadically (see <a href="troggle-ish.html">Troggle notes</a>).</p>
<p>After Expo 2009 the version control system was updated to hg (Mercurial), <p>After Expo 2009 the version control system was updated to a <a href="onlinesystems.html#mercurial">DVCS</a> (Mercurial, aka 'hg'),
because a distributed version control system makes a great deal of sense for expo because a distributed version control system makes a great deal of sense for expo
(where it goes offline for a month or two and nearly all the year's edits happen).</p> (where it goes offline for a month or two and nearly all the year's edits happen).</p>
@ -127,7 +127,7 @@ data was split into separate repositories: the website,
troggle, the survey data, the tunnel data. Seagrass was turned off at troggle, the survey data, the tunnel data. Seagrass was turned off at
the end of 2013, and the site has been hosted by Sam Wenham at the the end of 2013, and the site has been hosted by Sam Wenham at the
university since Feb 2014. university since Feb 2014.
In 2018 we have 4 repositories, see <a href="manual.html#repositoriesl">the website manual</a></p>. In 2018 we have 4 repositories, see <a href="manual.html#repositories">the website manual</a></p>.
<p>In spring 2018 Sam, Wookey and Paul Fox updated the Linux version and the Django version (i.e. troggle) to <p>In spring 2018 Sam, Wookey and Paul Fox updated the Linux version and the Django version (i.e. troggle) to
something vaguely acceptable to the university computing service and fixed all the problems that were then observed. something vaguely acceptable to the university computing service and fixed all the problems that were then observed.