expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2026-02-08 08:10:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

status updates

Browse Source
This commit is contained in:
Philip Sargent
2023-09-03 00:49:43 +03:00
parent 5e887901d5
commit 79bbc8719f
2 changed files with 15 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
handbook/troggle/trogstatus.html
View File

@@ -14,12 +14,6 @@
<p>For earlier history see <a href="../website-history.html">Website history</a>.
<h4>April 2021</h4>
<p>Covid lockdown has been good to troggle. During March and April Philip migrated troggle up to
<a href="../troggle/trogdjangup.html">Django 2.2.19</a>, excising the ancient and unused user registration system on the way. Django 2.2 LTS is a long-term stable relase which will be in-support by Django until April next year. Wookey discovered and ran the Django system testsuite on the Debian server thus enabling us to use a necessary (but obstensibly outdated) link between Django and the database MariaDB. As of April 9th troggle is now running on software which is actually 'in date'.</p>
<p>We plan to stick with this configuration for a year.</p>
<h4>March 2022</h4>
<p>On 15th March Wookey upgraded the server to the debian release 11 <var>bullseye</var>.
@@ -42,6 +36,17 @@ changed: survex files edited on a webpage now automatically commit to git with n
<p>Just before expo, we finished integrating the formerly-separate 'wallets' script.
So now the progress of scanning and tunneling survey data can be managed more easily. This
has turned out to be unexpectedly powerful. And it works on the data back to 1999 too.
<p>Wookey's replacment WiFi antenna (previously we had used Sam's) turned out to be useless, so internet access was not
available in the hut this year. This was a real pain.
<h4>July 2023</h4>
<p>Because Nadia asked nicely, we now have a rename form for uploaded files in wallets. This year we also have a 'create wallet' form.
<p>In the potato hut the blue netbook crashed horribly during expo and although Mark Shinwell coaxed it back to life, repreated fsck means that it needs to be retired before next year. The netbook was running Wookey's carefully curated drivers for the replacement USB-WiFi antenna which restored reasonable internet access in the hut this year.
<h4>September 2023</h4>
<p>
Too late for expo, but we now have a logbook entry creation and editing form running in a webpage.
Hopefully this will reverse the trend in recent years for many fewer people writing up trips in the logbook and many fewer trip records in general. The whiteboard at topcamp is a wonderful thing, but it gets erased so we no longer have a callout book permant record of trips.
<hr />
<img border="1" class="onright" width="150px" src='tricky-troggle.jpg' alt='git logo'/></a>
Return to: <br />

4
handbook/website-history.html
View File

@@ -272,6 +272,10 @@ In the course of these migrations several unused or partly-used django plugins w
<h4>July 2020</h4>
<p>Wookey upgraded debian on the server from 9 <var>stretch</var> to 10 <var>buster</var> and we got the python3 development of troggle running as the public version (with some http:// and https:// glitches) by 23rd July. <var>Buster</var> will be in-support definitely until June 2024 so we are rather pleased to be on a "not ancient" version of the operating system at last. This concided with a last tweak at improving the full cave data file import so now it runs on the development system in ~80 seconds. Which is considerably more useful than the ~5 hours it was taking earlier this year.
<h4>April 2021</h4>
<p>Covid lockdown has been good to troggle. During March and April Philip migrated troggle up to
<a href="../troggle/trogdjangup.html">Django 2.2.19</a>, excising the ancient and unused user registration system on the way. Django 2.2 LTS is a long-term stable relase which will be in-support by Django until April next year. Wookey discovered and ran the Django system testsuite on the Debian server thus enabling us to use a necessary (but obstensibly outdated) link between Django and the database MariaDB. As of April 9th troggle is now running on software which is actually 'in date'.</p>
<p>We plan to stick with this configuration for a year.</p>
<h3>More recent</h3>
<p>