mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2024-12-04 23:52:23 +00:00
78 lines
3.9 KiB
HTML
78 lines
3.9 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 .
|
|
</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>[Many website pages generated by troggle will fail for the new year you are creating 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>Create a new <var>expoweb</var> website folder e.g. /2023/ in
|
|
<ul>
|
|
<li>expoweb/years/
|
|
</ul>
|
|
<li>Update <a href="/infodx.htm">expoweb/infodx.htm</a> with the new year number (top and bottom)
|
|
<li>Update <a href="/pubs.htm">expoweb/pubs.htm</a> with the new year number
|
|
|
|
<li>edit <var>expoweb/index.htm</var> - edit the title and make it link to e.g. <var>expoweb/years/2022/</var>
|
|
<li>edit <var>troggle/templates/base.html</var> - change the title and add a link to this year's expo
|
|
<li>edit <var>troggle/templates/walletform.html</var> - change to this coming year
|
|
<li>copy the contents of the previous year's <var>expoweb/years/</var> folder, e.g. /2016/ to /2017/ 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>
|
|
</ul>
|
|
|
|
<h4>Whenever you like before Expo</h4>
|
|
<ul>
|
|
<li>Create new subfolders e.g. /2022/ in <var>expofiles/</var>, in each of
|
|
<ul>
|
|
<li>expofiles/writeups/
|
|
<li>expofiles/photos/
|
|
<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
|
|
</ul>
|
|
<li>Test that the bierbook and seshbook LaTeX scripts <var>expoweb/documents/bierbook</var> work on your machine</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/2022/</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>
|
|
|