boe split page

This commit is contained in:
Philip Sargent 2023-03-23 18:14:42 +00:00 committed by Wookey
parent eb48984e27
commit fae3faf21e
3 changed files with 62 additions and 46 deletions

View File

@ -23,49 +23,8 @@ The split mechanism transparently underlies everything, but for user-friendlines
<p>Source and docs for the upstream version are online at <a href="https://github.com/malc0/BoC">https://github.com/malc0/BoC</a> which has a link to a demonstration system that you can play with (CUCC meets 2014-15).</p>
<h2>Configure BOE for a new Expo</h2>
<p>You need to have a terminal running logged in to the server using ssh to do all this. Most expo treasurers will need to get a nerd to do this for them. Any Linux nerd, even if unfamiliar with boe, should be able to do all this if they have ssh access.
<p>In /home/expo/boe create a new folder for the data , e.g. for 2029:
<ul>
<li>/home/expo/boe/data/boe29
</ul>
and a new folder to hold last-year's code:
<ul>
<li>/home/expo/boe/boc-<b>2028</b>
</ul>
Copy everything from /home/expo/boe/boc/ into /home/expo/boe/boc-2028/
and then edit the first line of the file /home/expo/boe/boc/boc_config to read:
<pre>
Root /home/expo/boe/data/boe29
TemplateDir resources
#StyleURL /boe/boc/resources/bocstyle.css
#StyleURL /boe/boc/boc.pl?serve=bocstyle
#TimeoutURL /boe/boc/resources/timeout.js
</pre>
Now the code is in the place that the webserver expects it, and the code is configured to point to the new data for 2029.
Now copy everything in the most recent year from, e.g. /home/expo/boe/boc-2028/ into /home/expo/boe/boc-2029/ .
Then go into the folder /home/expo/boe/data/boe29/<b>users</b>/ and delete the files for all the users except for you and wookey.
(Assuming you were on expo in the previous year).
Edit your file to have the line
<pre>
IsAdmin
</pre>
<p>Now if you didn't create a password for last year's expo, create a password like this (Wookey will tell you what the 'salt' is):
<pre>
perl -e "use Crypt::PasswdMD5;print unix_md5_crypt('password','salt');"
</pre>
and put it in data/boe29/users/yourname and
git commit any changes.
<p>
From this point on all the configuration you do with be directly with the online BoE running on the server. Log in and check it all works.
<p>Now read the <a href="boc.pdf">the documentation</a> (PDF) (for the version running on the expo server).</p>
<h4>Configure BOE for a new Expo</h4>
<p> See <a href="boenewexpo.html">BOE nerd instructions</a>
<hr />
Go back to <a href="treasurer.html">Expo Treasurer Role</a><br>
Go on to <a href="bierbook.html">The Bier and Sesh books</a>

59
handbook/boenewexpo.html Normal file
View File

@ -0,0 +1,59 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf8" />
<title>CUCC Expedition Handbook: Bank of Expo</title>
<link rel="stylesheet" type="text/css" href="../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expedition Handbook</h2>
<h1>The Bank of Expo</h1>
<p>If you don't know what this is for, see <a href="bankofexpo.html">Bank of Expo</a>.
<h2>Configure BOE for a new Expo</h2>
<p>You need to have a terminal running logged in to the server using ssh to do all this. Most expo treasurers will need to get a nerd to do this for them. Any Linux nerd, even if unfamiliar with boe, should be able to do all this if they have ssh access.
<p>In /home/expo/boe create a new folder for the data , e.g. for 2029:
<ul>
<li>/home/expo/boe/data/boe29
</ul>
and a new folder to hold last-year's code:
<ul>
<li>/home/expo/boe/boc-<b>2028</b>
</ul>
Copy everything from /home/expo/boe/boc/ into /home/expo/boe/boc-2028/
and then edit the first line of the file /home/expo/boe/boc/boc_config to read:
<pre>
Root /home/expo/boe/data/boe29
TemplateDir resources
#StyleURL /boe/boc/resources/bocstyle.css
#StyleURL /boe/boc/boc.pl?serve=bocstyle
#TimeoutURL /boe/boc/resources/timeout.js
</pre>
Now the code is in the place that the webserver expects it, and the code is configured to point to the new data for 2029.
Now copy everything in the most recent year from, e.g. /home/expo/boe/boc-2028/ into /home/expo/boe/boc-2029/ .
Then go into the folder /home/expo/boe/data/boe29/<b>users</b>/ and delete the files for all the users except for you and wookey.
(Assuming you were on expo in the previous year).
Edit your file to have the line
<pre>
IsAdmin
</pre>
<p>Now if you didn't create a password for last year's expo, create a password like this (Wookey will tell you what the 'salt' is):
<pre>
perl -e "use Crypt::PasswdMD5;print unix_md5_crypt('password','salt');"
</pre>
and put it in data/boe29/users/yourname and
git commit any changes.
<p>
From this point on all the configuration you do with be directly with the online BoE running on the server. Log in and check it all works.
<p>Now read the <a href="boc.pdf">the documentation</a> (PDF) (for the version running on the expo server).</p>
<hr />
Go back to <a href="treasurer.html">Expo Treasurer Role</a><br>
Go on to <a href="bierbook.html">The Bier and Sesh books</a>
<hr /></body>
</html>

View File

@ -37,8 +37,6 @@
</ul>
<H2 id="thejob">Part 2: How to be Expo Treasurer</H2>
<P>This section details some things Earl found as Expo treasurer in 1999, since updated, which we hope will help you avoid some errors and worries. </P>
@ -56,7 +54,7 @@
<li>Publish the "Accounting Policy" for the forthcoming expo before April
<LI>Operate the Expo bank account. </LI>
<LI>Explore last year's <a href="http://expo.survex.com/boe/boc.pl">Online Bank of Expo</a> data to see how it all works</a> </LI>
<LI>Then, create the <a href="bankofexpo.html">Bank of Expo</a> for this next year - you may need a nerd <a href="../documents/bierbook/readme.txt">to help you</a> </LI>
<LI>Then, create the <a href="bankofexpo.html">Bank of Expo</a> for this next year - you may need a nerd <a href="boenewexpo.html">to help you</a> </LI>
<LI>Create the <a href="bierbook.html">Expo Bier Book and Sesh Book</a> when you know most of the people have signed up - you may need a nerd to help you </LI>
<LI>Process the Expo Bier Book and Sesh Book through Bank of Expo to produce Expo Bills. </LI>
<LI>As far as possible, maintain or improve the financial health of Expo. </LI>