mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2024-12-22 08:22:22 +00:00
85 lines
5.1 KiB
HTML
85 lines
5.1 KiB
HTML
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<title>CUCC Expedition Handbook: Programmers manual</title>
|
|
<link rel="stylesheet" type="text/css" href="/css/main2.css" />
|
|
</head>
|
|
<body>
|
|
<style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
|
|
<h2 id="tophead">CUCC Expedition Handbook - Online systems</h2>
|
|
<h1>New Expo Maintenance - Creating a New Year</h1>
|
|
|
|
<h2><a id="manual">Creating a New Year in the Expo online systems</a></h2>
|
|
|
|
<ul>
|
|
|
|
<li>This page <i>is a checklist for programmers</i> who are configuring the systems for next year's expo .
|
|
<li>We are steadily automating these tasks, so the list is shorter every year.
|
|
</ul>
|
|
|
|
<h3>Adding a new year in 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. Changes to <var>:expoweb:</var> and <var>:troggle:</var> must be done using the version control
|
|
system as these are <a href="../computing/repos.html">repositories</a>.
|
|
<p>Several troggle pages will automatically notice that it is after 31st December in the year of the most recent expedition, and will helpfully create the things you need for the coming expedition. Not everything though.
|
|
<p>Some website pages generated by troggle will fail for the new yearnext expedition until you do the folk-update process
|
|
to create a new year column (see below). ]
|
|
|
|
|
|
<h4>Well before Expo as these pages are used in planning</h4>
|
|
<ul>
|
|
<li>Manually edit these HTML pages as lots of other pages link to them and they are not troggle pages. Longer job, replace each of these hard-coded HTML pages with a troggle page.
|
|
<ul>
|
|
<li>Edit <a href="/infodx.htm">expoweb/infodx.htm</a> with the new year number (top and bottom). - 130 pages link to this...
|
|
<li>Edit <a href="/pubs.htm">expoweb/pubs.htm</a> with the new year number. - 165 pages link to this...
|
|
<li><strike>Edit <a href="/index.htm">expoweb/index.htm</a> - edit the title and make it link to e.g. <var>expoweb/years/2025/</var> - 1,212 pages link to this...</strike>
|
|
<li>Edit <a href="/years/index.htm">expoweb/years/index.htm</a> with the new year number. - 413 pages link to this.
|
|
</ul>
|
|
|
|
|
|
|
|
<li>Manually copy the contents of the previous year's <var>expoweb/years/</var> folder, e.g. /2024/ to /2025/ and edit all the files therein. You should start with at least an index.html and a mission.html
|
|
<li>edit <var>expoweb/folk/folk.csv</var> - see below - just to add a column for the coming year. Until that year column exists, the online system will be unaware that there is an expedition that year.
|
|
<li>Create the Bank of Expo <a href="../bankofexpo.html"><var>boe</var></a> for the expected attendees.
|
|
This is done directly in an <var>ssh</var> terminal session on the server.</li>
|
|
<li><strike>edit <var>troggle/templates/base.html</var> - change the title and add a link to this year's expo. </strike> Now automatic, after 31st Dec.
|
|
<li><strike>edit <var>troggle/templates/walletform.html</var> - change to this coming year</strike> Now automatic, after 31st Dec.
|
|
<li><strike>edit <var>/expedition</var> - change to this coming year</strike> Now automatic, after 31st Dec.
|
|
|
|
<li><strike>Create a new <var>expoweb</var> website folder e.g. /2025/ in <var>expoweb/years/</var></strike> Now automatic, after 31st Dec.
|
|
</ul>
|
|
|
|
<h4>Whenever you like before Expo</h4>
|
|
<ul>
|
|
<li>Create new subfolders e.g. /2025/ in <var>expofiles/</var>, in each of
|
|
<ul>
|
|
<li>expofiles/writeups/
|
|
|
|
<li>expofiles/gpslogs/
|
|
<li>expofiles/accounts/ - optional. Used for archiving after expo.
|
|
<li>expofiles/videos/ - optional. We don't do this much.
|
|
<li><s>expofiles/surveyscans/</s> - this now happens automatically when a wallet is created
|
|
<li><strike>expofiles/photos/</strike> Now automatic, after 31st Dec. </ul>
|
|
<li>Test that the bierbook and seshbook LaTeX scripts <a href="/documents/bierbook"><var>expoweb/documents/bierbook</var></a> work on your machine. Or use an online LaTeX system to generate them, e.g. <a href="https://www.overleaf.com/user/subscription/plans">Overleaf.com</a> (free plan, for the moment)</li>
|
|
|
|
</ul>
|
|
|
|
<h4>A week or so before Expo</h4>
|
|
<ul>
|
|
<li>create initial versions of the bierbook and the seshbook in <var>expoweb/documents/bierbook</var>
|
|
(the final copies after expo will be scanned and put in
|
|
e.g. <var>expofiles/writeups/2025/</var> along with the scanned logbook). These need an updated <var>names.txt</var> file of expoers.</li>
|
|
<li>update the gear tape colours for the expected expoers in <a href="../geartape.html"><var>/expoweb/handbook/geartape.html</var></a> </li>
|
|
<li>edit <var>expoweb/folk/folk.csv</var> - see below - to add people. Until a name is recorded in the Folk file that person will not be recognised within the online system as a cave surveyor or logbook entry writer.</li>
|
|
</ul>
|
|
<p>Edit <var>expoweb/folk/folk.csv</var> according to the instructions in the <a href="folkupdate.html">Folk Update process</a>.
|
|
</p>
|
|
|
|
Return to the main <a href="manual.html">online systems manual</a>.
|
|
|
|
<hr /></body>
|
|
</html>
|
|
|