current year auto

This commit is contained in:
Philip Sargent 2024-03-15 01:52:25 +00:00
parent 82af5fa109
commit 57919fffdb

View File

@ -23,7 +23,8 @@
<p>There is no script to do this (yet). In the list below everything in expofiles is done by directly <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 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>. 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 <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). ] to create a new year column (see below). ]
@ -37,15 +38,16 @@ to create a new year column (see below). ]
</ul> </ul>
<li><strike>edit <var>troggle/templates/base.html</var> - change the title and add a link to this year's expo. </strike> &nbsp; Now automatic, after 31st Dec. <li><strike>edit <var>troggle/templates/base.html</var> - change the title and add a link to this year's expo. </strike> &nbsp; Now automatic, after 31st Dec.
<li>edit <var>troggle/templates/walletform.html</var> - change to this coming year <li><strike>edit <var>troggle/templates/walletform.html</var> - change to this coming year</strike> &nbsp; Now automatic, after 31st Dec.
<li><strike>edit <var>/expedition</var> - change to this coming year</strike> &nbsp; Now automatic, after 31st Dec.
<li><strike>Create a new <var>expoweb</var> website folder e.g. /2025/ in <var>expoweb/years/</var></strike> &nbsp; Now automatic, after 31st Dec.
<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>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>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. <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> This is done directly in an <var>ssh</var> terminal session on the server.</li>
<li>Create a new <var>expoweb</var> website folder e.g. /2025/ in
<ul>
<li>expoweb/years/
</ul>
</ul> </ul>
<h4>Whenever you like before Expo</h4> <h4>Whenever you like before Expo</h4>