mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2024-11-22 23:31:56 +00:00
58 lines
3.2 KiB
HTML
58 lines
3.2 KiB
HTML
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<title>Handbook Troggle Status</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</h2>
|
|
<h1>Troggle & Expo Systems - status update</h1>
|
|
<p>Troggle is the software which runs the the expo cave survey data management and website.
|
|
|
|
<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>.
|
|
At this point 'debian stable' is bullseye and has python 3.9 as
|
|
standard. We will quickly migrate to Django 3.2 LTS which is now a year old and which will be <a
|
|
href="https://www.djangoproject.com/download/#supported-versions">supported until April 2024</a>.
|
|
<var>Bullseye</var> will be <a href="https://wiki.debian.org/LTS">in support until June 2026</a>.
|
|
|
|
<p>Django migrations are not nearly as painful as they used to be, and troggle is already compatible with Django 4.0.3 (though we won't use that).
|
|
So the presure to migrate from Django is now very greatly lessened. However, see <a href="trogspeculate.html">troggle architecture speculations</a>
|
|
and possible <a href="trog2030.html">migration from Django</a>.
|
|
|
|
|
|
<p>We should not need to anything until we move from Django 3.2 LTS to 4.2 LTS before April 2024.
|
|
|
|
<h4>July 2022</h4>
|
|
<p>Wookey at last, after much effort, got the loser repository converted from mercurial to git, with much tidying and
|
|
history-reconfabulation. He says this will need to be done again, but it was good enough for the 2022 Expo. Also the troggle code was
|
|
changed: survex files edited on a webpage now automatically commit to git with no user involvement.
|
|
<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.
|
|
<hr />
|
|
<img border="1" class="onright" width="150px" src='tricky-troggle.jpg' alt='git logo'/></a>
|
|
Return to: <br />
|
|
<a href="../website-history.html">Website history</a><br /><br /><br />
|
|
Go on to: <a href="trogarch.html">Troggle architecture</a><br />
|
|
Return to: <a href="trogintro.html">Troggle intro</a><br /><br />
|
|
Troggle index:
|
|
<a href="trogindex.html">Index of all troggle documents</a><br /><hr />
|
|
|
|
<br />
|
|
|
|
<hr /></body>
|
|
</html>
|