expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-12-08 06:45:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

finishing the separation of the New Year page

Browse Source
This commit is contained in:
Philip Sargent
2019-12-29 00:58:36 +00:00
parent 6192de94b4
commit 9593daf39c
2 changed files with 16 additions and 52 deletions
Download Patch File Download Diff File Expand all files Collapse all files

51
handbook/manual.html
View File

@@ -255,56 +255,25 @@ superseded in 2012).</p>
<h3><a id="updatingyears">Updating expo year pages</a></h3>
<p>Each year's expo has a documentation index which is in the folder</p>
<p>Each year's expo is recorded in the folder</p>
<tt>/expoweb/years</tt>
<tt>/expoweb/years/</tt>
<p>so to checkout the 2011 page, for example, you would use</p>
<p>which contains a number of files used to manage and record that year's expo. Have a look at expoweb/years/2018/ for a recent well-documented expo (the weather was good). Files are added and edited using the version control system for the expoweb repository.</p>
<p>hg clone ssh://expo@expo.survex.com/expoweb/years/2011</tt></p>
<p>To create a new 'year' for next year's expo see <a href="computing/newyear.html">adding a new year</a>.
<p> Once you have pushed your changes to the repository you need to update the server's local copies, by ssh into the server and running hg update in the expoweb folder. </p>
<h3>Adding a new yearin the Expo online systems</h3>
<p>There is no script to do this (yet). In the list below everything in expofiles is done by directly overwriting what is on the server. Chnages to expoweb and troggle must be done using the version control system as these are repositories.
<ul>
<li>Create a new folder e.g. /2020/ in each of
<ul>
<li>expoweb/years/
<li>expoweb/accounts/
<li>expofiles/videos/ - optional. We don't do this much.
<li>expofiles/writeups/
<li>expofiles/photos/
<li>expofiles/gpslogs/
<li>expofiles/surveyscans/
</ul>
<li>copy wallets.py from the previous year's folder in expofiles/surveyscans/ into the current year
<li>create 50 folders in the new surveyscans year folder e.g. in expofiles/surveyscans/2020/ of the form /2020#01/, /2020#02/ etc.
<li>edit /expoweb/index.htm - edit the title and make it link to e.g. expoweb/years/2020/
<li>edit expoweb/folk/folk.csv - see below
<li>edit troggle/templates/base.html - change the title and adda link to this year's expo
<li>create initial versions of the bierbook and the seshbook in expoweb/documents/bierbook
<li>copy the contents of the previous year's expoweb/years/ folder, e.g. /2019/ to 2020/ and edit all the files therein. You should start with at least an index.html and a mission.html
</ul>
<p>Edit folk/folk.csv, adding the new year to the end of the header
line, a new column, with just a comma (blank
cell) for people who weren't there, a 1 for people who were there, and
a -1 for people who were there but didn't go caving. Add new lines for
new people, with the right number of columns.</p>
<p>This proces is tedious and error-prone and ripe for improvement.
Adding a list of people, from the bier book, and their aliases would be
a lot better, but some way to make sure that names match with previous
years would be
good.</p>
<h3><a id="surveystatus">Maintaining the survey status table</a></h3>
<p>See the <a href="survey/onlinewallet.html">documentation</a> on updating the online surveyscans folders using the lever-arch file of plastic wallets.
<p>There is a table in the survey book which has a list of all the surveys and whether or not they have been drawn up, and some other info.</p>
<p>This is generated by the script tablizebyname-csv.pl from the input file Surveys.csv</p>
<p> This below is obsolete:
<ul>
<li>There was a table in the survey book which has a list of all the surveys and whether or not they have been drawn up, and some other info.
<li>This used to be generated by the script tablizebyname-csv.pl from the input file Surveys.csv
</ul>
<hr />
</body>

17
handbook/onlinesystems.html
View File

@@ -28,12 +28,11 @@ fuller list of "How do I..." instruction pages are on <a href="index.htm">the ha
<li><a href="logbooks.html">Uploading typed logbooks</a></li>
<li><a href="gpxupload.html">Uploading GPS tracks</a></li>
<li><a href="survey/newcave.html">Recording a new cave discovery</a></li>
<li><a href="survey/status.html">Monitoring the status cave survey workflow during and after expo</a></li>
<li><a href="survey/status.html">Monitoring the status of the cave survey workflow during and after expo</a></li>
</ul>
<p>But the systems Manual is still being actively edited to extract and simplify documentation. At the moment
it is the only documentation we have for:
<p>But the systems Manual is still being actively edited to extract and simplify documentation.
<ul>
<li><a href="manual.html#update">Manual: Creating a new 'year' in the system</a></li>
<li><a href="computing/newyear.html">Manual: Creating a new 'year' in the system</a></li>
<li><a href="manual.html#update">Manual: Updating the cave guidebook descriptions</a></li>
<li><a href="manual.html#manual">Manual: Expo software and server maintenance manual</a></li>
</ul>
@@ -89,10 +88,6 @@ mechanism does not tidy-up after itself properly.
See <a href="manual.html#editthispage">these instructions for this tidy-up</a>
<h3 id="mercurial">DVCS - version control</a></h3>
<p>We use a distributed revision control system (DVCS) for all the important data.
This means that many people can edit and merge their changes with the expo
@@ -108,9 +103,8 @@ then get synchronised when it next gets internet access.
do not get modified, so they are kept as a plain directory of files 'expofiles'.
The same goes for holiday photographs and GPS logs.</p>
<p>In 2019 we had half our <a href="manual.html#repositories">version-controlled repositories</a> under mercurial and half under git.
The intention is to move entirely to git before the 2020 expo.
<h3 id="troggle">Troggle - what it is</a></h3>
@@ -128,6 +122,7 @@ and publish it on the web.
<li><a href="http://expo.survex.com/survey_scans/">expo.survex.com/survey_scans/</a> - List of all scanned original survey notes.
<li><a href="http://expo.survex.com/survey_scans/2018%252343/">expo.survex.com/survey_scans/2018%252343/</a> - list of links to scanned notes for wallet #43 during the 2018 expo.
</ul>
<p>[Note that /survey_scans/ is generated by troggle and is not the same thing as /expofiles/surveyscans/ at all.]
<p>Only a small part of troggle's original plan was fully implemented and deployed.
Many of the things it was intended to replace are still operating as a motley collection written by many different people in
several languages (but mostly perl and python; we won't talk about the person who likes to use OCamL).